aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* In a machine where INT64_IS_BUSTED, we can only support 32-bit valuesTom Lane2005-09-24
| | | | | | | for int8 and related types. However we might be talking to a client that has working int64; so pq_getmsgint64 really needs to check the incoming value and throw an overflow error if we can't represent it accurately.
* Add comments explaining clauses used by CREATE ROLE but not ALTER.Bruce Momjian2005-09-23
|
* Fix typo in comment.Tom Lane2005-09-23
|
* Fix bug introduced into indexable_outerrelids() by an ill-consideredTom Lane2005-09-22
| | | | | | | | | | "optimization". When we find a potentially useful joinclause, we have to add all its other required_relids to the result, not only the other clause_relids. They are different in the case of a joinclause whose applicability has to be postponed due to outer join. We have to include the extra rels because otherwise, after best_inner_indexscan masks the join rels with index_outer_relids, it will always fail to find the joinclause as applicable. Per report from Husam Tomeh.
* Add instructions.Bruce Momjian2005-09-22
|
* Add "codelines" script to compute number of lines in a releaes.Bruce Momjian2005-09-22
|
* pgindent new GIST index code, per request from Tom.Bruce Momjian2005-09-22
|
* Adjust GiST error messages to conform to message style guidelines.Tom Lane2005-09-22
|
* Take exclusive buffer lock in scan_heap() to eliminate some corner casesTom Lane2005-09-22
| | | | | | | | in which invalid page data could be transiently written to disk by concurrent bgwriter activity. There doesn't seem any risk of loss of actual user data, but an empty page could possibly be left corrupt if a crash occurs before the correct data gets written out. Pointed out by Alvaro Herrera.
* This patch cleans up the access to members of ItemIdData.Bruce Momjian2005-09-22
| | | | | | It uses existing macros instead of touching directly. ITAGAKI Takahiro
* Fix psql \x by removing puts().Bruce Momjian2005-09-22
| | | | Greg Sabino Mullane
* Suppress port number for unix domain sockets in log connect/disconnectBruce Momjian2005-09-22
| | | | messages.
* Remove some dead code.Tom Lane2005-09-22
|
* Fix postgresql.conf lexer to accept doubled single quotes in literalTom Lane2005-09-21
| | | | | | strings. This is consistent with SQL conventions, and since Bruce already changed initdb in a way that assumed it worked like this, seems we'd better make it work like this.
* Suppress database dump item when --table and/or --schema switch wasTom Lane2005-09-21
| | | | given, per gripe from Michael Fuhr.
* optimize_minmax_aggregates() neglected to check for inherited tables.Tom Lane2005-09-21
| | | | Per report from Cesar Paipilla.
* Fix interaction between psql \set AUTOCOMMIT and "ON_ERROR_ROLLBACK"Bruce Momjian2005-09-20
| | | | by properly updating transaction state after AUTOCOMMIT.
* Return proper value for psql -f filename failure if filename open fails.Bruce Momjian2005-09-20
| | | | Backpatch to 8.0.X.
* autovacuum setting false -> off, for consistencyBruce Momjian2005-09-20
|
* Print proper cause of statement cancel, user interaction or timeout.Bruce Momjian2005-09-19
|
* Clarify some error messagesPeter Eisentraut2005-09-18
|
* Adjust regression for new cancel query message.Bruce Momjian2005-09-16
|
* Update query cancel message:Bruce Momjian2005-09-16
| | | | errmsg("canceling query due to user request or statement timeout")));
* Adjust bcc to work for thread changes.Bruce Momjian2005-09-16
|
* This correction is required of nmake of Windows.Bruce Momjian2005-09-16
| | | | Hiroshi Saito
* Small fixesTeodor Sigaev2005-09-16
|
* Rename pg_complete_relation_size() to pg_total_relation_size(), for theNeil Conway2005-09-16
| | | | | | | | | | | | | | sake of brevity and clarity. Make pg_reload_conf(), pg_rotate_logfile(), and pg_cancel_backend() return a boolean rather than an integer to indicate success or failure. Along the way, make some minor cleanups to dbsize.c -- in particular, use elog() rather than ereport() for "shouldn't happen" error conditions, and remove some of the more flagrant violations of the Postgres indentation conventions. Catalog version bumped.
* Update two comments to refer to use the new list API names.Neil Conway2005-09-16
|
* Force the size and alignment of LWLock array entries to be either 16 or 32Tom Lane2005-09-16
| | | | | | | bytes. This shouldn't make any difference on x86 machines, where the size happened to be 16 bytes anyway, but on 64-bit machines and machines with slock_t int or wider, it will speed array indexing and hopefully reduce SMP cache contention effects. Per recent experimentation.
* Copy-editing for GiST README.Neil Conway2005-09-15
|
* Readme about GiST's algorithmsTeodor Sigaev2005-09-15
|
* Tweak the PL/PgSQL regression tests to catch the recently reported bugNeil Conway2005-09-14
| | | | in parsing cursor declarations.
* Fix recent breakage of decl_cursor_arglist syntax, per Michael Paesold.Tom Lane2005-09-14
|
* Fix make_tuple_from_row to support nested rowtypes, per gripe fromTom Lane2005-09-13
| | | | Roman Neuhauser. Update some obsolete comments for exec_eval_datum, too.
* Ensure that any memory leaked during an error inside the bgwriter isTom Lane2005-09-12
| | | | | | | recovered. I did not see any actual leak while testing this in CVS tip, but 8.0 definitely has a problem with leaking the space temporarily palloc'd by BufferSync(). In any case this seems a good idea to forestall similar problems in future. Per report from Arjen van der Meijden.
* Fixed transaction command handling to not ignore savepoints and to correctly ↵Michael Meskes2005-09-12
| | | | check for errors.
* Tweak TCP-keepalive code so that an invalid setting doesn't cause usTom Lane2005-09-12
| | | | | | | to drop connections unceremoniously. Also some other marginal cleanups: don't query getsockopt() repeatedly if it fails, and avoid having the apparent definition of struct Port depend on which system headers you might have included or not. Oliver Jowett and Tom Lane.
* Fix some corner-case bugs in _sendSQLLine's parsing of SQL commandsTom Lane2005-09-11
| | | | | | | | | > found in a pg_dump archive. It had problems with dollar-quote tags broken across bufferload boundaries (this may explain bug report from Rod Taylor), also with dollar-quote literals of the form $a$a$..., and was also confused about the rules for backslash in double quoted identifiers (ie, they're not special). Also put in placeholder support for E'...' literals --- this will need more work later.
* Avoid changing stdin/stdout to binary mode on Windows unless that isTom Lane2005-09-11
| | | | | | | really the source or destination of the archive. I think this will resolve recent complaints that password prompting is broken in pg_restore on Windows. Note that password prompting and reading from stdin is an unworkable combination on Windows ... but that was true anyway.
* Given its current definition that depends on time(NULL), timetz_zoneTom Lane2005-09-09
| | | | | | | | | is certainly no longer immutable, but must indeed be marked volatile. I wonder if it should use the value of now() (that is, transaction start time) so that it could be marked stable. But it's probably not important enough to be worth changing the code for ... indeed, I'm not even going to force an initdb for this catalog change, seeing that we just did one a few hours ago.
* timestamptz_izone should return the input, not NULL, when the inputTom Lane2005-09-09
| | | | | | is a non-finite timestamp, for consistency with related functions. In other words: +infinity rotated to a different timezone is still +infinity.
* Fix the various forms of AT TIME ZONE to accept either timezones foundTom Lane2005-09-09
| | | | | | | | | in the zic database or zone names found in the date token table. This preserves the old ability to do AT TIME ZONE 'PST' along with the new ability to do AT TIME ZONE 'PST8PDT'. Per gripe from Bricklen Anderson. Also, fix some inconsistencies in usage of TZ_STRLEN_MAX --- the old code had the potential for one-byte buffer overruns, though given alignment considerations it's unlikely there was any real risk.
* Create the pg_pltemplate system catalog to hold template informationTom Lane2005-09-08
| | | | | | for procedural languages. This replaces the hard-wired table I had originally proposed as a stopgap solution. For the moment, the initial contents only include languages shipped with the core distribution.
* Update regression tests for new USA timezone data. Mea culpa for notTom Lane2005-09-08
| | | | realizing that the regression tests could be affected.
* Update timezone data files to release 2005m of the zic database.Tom Lane2005-09-07
| | | | | Among other changes, this reflects the recently passed change in USA daylight savings rules.
* Implement a preliminary 'template' facility for procedural languages,Tom Lane2005-09-05
| | | | | | | | | | | | | | as per my recent proposal. For now the template data is hard-wired in proclang.c --- this should be replaced later by a new shared system catalog, but we don't want to force initdb during 8.1 beta. This change lets us cleanly load existing dump files even if they contain outright wrong information about a PL's support functions, such as a wrong path to the shared library or a missing validator function. Also, we can revert the recent kluges to make pg_dump dump PL support functions that are stored in pg_catalog. While at it, I removed the code in pg_regress that replaced $libdir with a hardcoded path for temporary installations. This is no longer needed given our support for relocatable installations.
* Back out prior patch and instead just suppress SubqueryScan eliminationTom Lane2005-09-05
| | | | | | | | when there are extra resjunk columns in the child node. I found some additional cases involving Append nodes that weren't handled by the prior patch, and it's not clear how to fix them in the same way without breaking inheritance cases. So the prudent path seems to be to narrow the scope of the optimization.
* Clean up version comparison/display code, per gripe from Michael Fuhr.Tom Lane2005-09-05
|
* For non-projecting plan node types such as Limit, set_plan_referencesTom Lane2005-09-05
| | | | | | has to recopy the input plan node's targetlist if it removes a SubqueryScan node just below the non-projecting node. For simplicity I made it recopy always. Per bug report from Allan Wang and Michael Fuhr.
* Conditionally output the server version number in psql if it doesn'tBruce Momjian2005-09-05
| | | | | exactly match the client version number, and warn about major version mismatches.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 14:25:22 +0000