aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Add missing check on invocation of trusted procedures.Robert Haas2011-04-04
| | | | KaiGai Kohei
* Include pid in pg_lock_status() results even for SIREAD locks.Robert Haas2011-04-04
| | | | Dan Ports
* Duplicate expansion of "direction" from FETCH's synopsis into MOVEAlvaro Herrera2011-04-04
|
* Rearrange "add column" logic to merge columns at exec time.Robert Haas2011-04-03
| | | | | | | | | The previous coding set attinhcount too high in some cases, resulting in an undumpable, undroppable column. Per bug #5856, reported by Naoya Anzai. See also commit 31b6fc06d83c6de3644c8f2921eb7de0eb92fac3, which fixes a similar bug in ALTER TABLE .. ADD CONSTRAINT. Patch by Noah Misch.
* Improve documentation on the range of the numeric data type.Robert Haas2011-04-03
| | | | Gianni Ciolli, reviewed by Noah Misch
* Remove mention of using "man" from the tutorial.Robert Haas2011-04-03
| | | | | | | This isn't applicable on Windows, and the internal link to the psql documentation should be more than sufficient. Susanne Ebrecht
* Avoid possible hang during smart shutdown.Robert Haas2011-04-03
| | | | | | | | | | | | | | | If a smart shutdown occurs just as a child is starting up, and the child subsequently becomes a walsender, there is a race condition: the postmaster might count the exstant backends, determine that there is one normal backend, and wait for it to die off. Had the walsender transition already occurred before the postmaster counted, it would have proceeded with the shutdown. To fix this, have each child that transforms into a walsender kick the postmaster just after doing so, so that the state machine is certain to advance. Fujii Masao
* Fix typo in PQconnectStartParams().Tom Lane2011-04-02
| | | | | | | | This would lead to leaking the PGconn structure after an error detected by conninfo_array_parse(), as well as failing to return a useful error message in such cases. Backpatch to 9.0 where the error was introduced. Joseph Adams
* Escape greater than and less than characters in docs.Heikki Linnakangas2011-04-02
| | | | Susanne Ebrecht and me
* Avoid palloc before CurrentMemoryContext is set up on win32Magnus Hagander2011-04-01
| | | | | | | Instead, write the unconverted output - it will be in the wrong encoding, but at least we don't crash. Rushabh Lathia
* Tab completion for COMMENT ON FOREIGN DATA WRAPPER / SERVER.Robert Haas2011-04-01
|
* pg_dump support for comments on FOREIGN DATA WRAPPER and SERVER objects.Robert Haas2011-04-01
| | | | Shigeru Hanada, with some corrections.
* Support comments on FOREIGN DATA WRAPPER and SERVER objects.Robert Haas2011-04-01
| | | | | | | | | | This mostly involves making it work with the objectaddress.c framework, which does most of the heavy lifting. In that vein, change GetForeignDataWrapperOidByName to get_foreign_data_wrapper_oid and GetForeignServerOidByName to get_foreign_server_oid, to match the pattern we use for other object types. Robert Haas and Shigeru Hanada
* Fix compiler warning.Robert Haas2011-04-01
|
* Fix two missing spaces in error messages.Heikki Linnakangas2011-04-01
| | | | Josh Kupershmidt
* Fix a tiny race condition in predicate locking. Need to hold the lock whileHeikki Linnakangas2011-03-31
| | | | | | | | examining the head of predicate locks list. Also, fix the comment of RemoveTargetIfNoLongerUsed, it was neglected when we changed the way update chains are handled. Kevin Grittner
* Increase SHMEM_INDEX_SIZE from 32 to 64. We're currently at 40 entries inHeikki Linnakangas2011-03-31
| | | | | | ShmemIndex, so 64 leaves some headroom. Kevin Grittner
* Don't leak the temporary PLyProcedure struct we create for inline plpythonHeikki Linnakangas2011-03-31
| | | | | | blocks. Investigation by Jan Urbański, though I didn't use his patch.
* Reword the phrase on zero replication_timeout in the docs.Heikki Linnakangas2011-03-31
|
* Improve error message when WAL ends before reaching end of online backup.Heikki Linnakangas2011-03-31
|
* Mention pg_upgrade sets autovacuum_freeze_max_age to maximum.Bruce Momjian2011-03-30
|
* Expand comment on how pg_upgrade is turning off autovacuum.Bruce Momjian2011-03-30
|
* Attempt to unbreak windows builds broken by commit 754baa2.Andrew Dunstan2011-03-30
|
* Check that we've reached end-of-backup also when we're not performingHeikki Linnakangas2011-03-30
| | | | | | | | | | | | | | archive recovery. It's possible to restore an online backup without recovery.conf, by simply copying all the necessary WAL files to pg_xlog. "pg_basebackup -x" does that too. That's the use case where this cross-check is useful. Backpatch to 9.0. We used to do this in earlier versins, but in 9.0 the code was inadvertently changed so that the check is only performed after archive recovery. Fujii Masao.
* Automatically terminate replication connections that are idle for moreHeikki Linnakangas2011-03-30
| | | | | | | | | than replication_timeout (a new GUC) milliseconds. The TCP timeout is often too long, you want the master to notice a dead connection much sooner. People complained about that in 9.0 too, but with synchronous replication it's even more important to notice dead connections promptly. Fujii Masao and Heikki Linnakangas
* Adjust error message, now that we expect other message types than connectionHeikki Linnakangas2011-03-30
| | | | | | close at this point. Fix PQsetnonblocking() comment. Fujii Masao
* Update SQL features listPeter Eisentraut2011-03-29
| | | | | | | | | Feature F692 "Extended collation support" is now also supported. This refers to allowing the COLLATE clause anywhere in a column or domain definition instead of just directly after the type. Also correct the name of the feature in accordance with the latest SQL standard.
* In pg_upgrade, add C comment about how autovacuum is disabled.Bruce Momjian2011-03-29
|
* Add maintainer-check targetPeter Eisentraut2011-03-28
| | | | | | This can do various source code checks that are not appropriate for either the build or the regression tests. Currently: duplicate_oids, SGML syntax and tabs check, NLS syntax check.
* Make duplicate_oids return nonzero exit status if duplicates were foundPeter Eisentraut2011-03-28
| | | | Automatic detection of errors is easier that way.
* Prevent a rowtype from being included in itself.Tom Lane2011-03-28
| | | | | | | | | | | | | | | | Eventually we might be able to allow that, but it's not clear how many places need to be fixed to prevent infinite recursion when there's a direct or indirect inclusion of a rowtype in itself. One such place is CheckAttributeType(), which will recurse to stack overflow in cases such as those exhibited in bug #5950 from Alex Perepelica. If we were sure it was the only such place, we could easily modify the code added by this patch to stop the recursion without a complaint ... but it probably isn't the only such place. Hence, throw error until such time as someone is excited enough about this type of usage to put work into making it safe. Back-patch as far as 8.3. 8.2 doesn't have the recursive call in CheckAttributeType in the first place, so I see no need to add code there in the absence of clear evidence of a problem elsewhere.
* Add 9.1 release note link for synchronous replication.Bruce Momjian2011-03-28
| | | | We already had links to the GUC variables that control it.
* Mark up release notes using <link>.REL9_1_ALPHA5Robert Haas2011-03-28
| | | | Unlike <xref>, this actually works.
* Add missing #includeAlvaro Herrera2011-03-28
|
* Get rid of links that don't work when building HISTORY.Tom Lane2011-03-28
|
* Typo fix in SSI docs.Robert Haas2011-03-27
| | | | Kevin Grittner
* Correct "characters" to "bytes" in createdb docs.Robert Haas2011-03-27
| | | | Susanne Ebrecht
* fix up a couple non-prototypes of the form foo() to be foo(void) -- found ↵Greg Stark2011-03-27
| | | | using -Wstrict-prototypes
* Fix check_exclusion_constraint() to insert correct collations in ScanKeys.Tom Lane2011-03-27
|
* Fix plpgsql to release SPI plans when a function or DO block is freed.Tom Lane2011-03-27
| | | | | | | | | | This fixes the gripe I made a few months ago about DO blocks getting slower with repeated use. At least, it fixes it for the case where the DO block isn't aborted by an error. We could try running plpgsql_free_function_memory() even during error exit, but that seems a bit scary since it makes a lot of presumptions about the data structures being in good shape. It's probably reasonable to assume that repeated failures of DO blocks isn't a performance-critical case.
* Remove disclaimer stating that fsync=off slows down sync rep.Robert Haas2011-03-26
| | | | | The underlying problem that caused this phenomenon was fixed by commit 92f4786fa9b730fd12cbfe973eb96addc6e98924.
* Update release notes for latest commits.Robert Haas2011-03-26
| | | | | In addition, correct the entry for pg_object_description, and some other minor cleanup.
* Clean up cruft around collation initialization for tupdescs and scankeys.Tom Lane2011-03-26
| | | | | I found actual bugs in GiST and plpgsql; the rest of this is cosmetic but meant to decrease the odds of future bugs of omission.
* More collations cleanup, from trawling for missed collation assignments.Tom Lane2011-03-26
| | | | | Mostly cosmetic, though I did find that generateClonedIndexStmt failed to clone the index's collations.
* Clean up a few failures to set collation fields in expression nodes.Tom Lane2011-03-26
| | | | | | | | | I'm not sure these have any non-cosmetic implications, but I'm not sure they don't, either. In particular, ensure the CaseTestExpr generated by transformAssignmentIndirection to represent the base target column carries the correct collation, because parse_collate.c won't fix that. Tweak lsyscache.c API so that we can get the appropriate collation without an extra syscache lookup.
* Additional test for each commit in sync rep path to plug minuteSimon Riggs2011-03-26
| | | | | possibility of race condition that would effect performance only. Requested by Robert Haas. Re-arrange related comments.
* Pass collation to makeConst() instead of looking it up internally.Tom Lane2011-03-25
| | | | | | | | | In nearly all cases, the caller already knows the correct collation, and in a number of places, the value the caller has handy is more correct than the default for the type would be. (In particular, this patch makes it significantly less likely that eval_const_expressions will result in changing the exposed collation of an expression.) So an internal lookup is both expensive and wrong.
* Fix failure to propagate collation in negate_clause().Tom Lane2011-03-25
| | | | | Turns out it was this, and not so much plpgsql, that was at fault in Stefan Huehner's collation-error-in-a-trigger bug report of a couple weeks ago.
* Document collation handling in SQL and plpgsql functions.Tom Lane2011-03-25
| | | | This is pretty minimal but covers the bare facts.
* Fix collation handling in plpgsql functions.Tom Lane2011-03-25
| | | | | | | | | | | | | | | | | | | Make plpgsql treat the input collation as a polymorphism variable, so that we cache separate plans for each input collation that's used in a particular session, as per recent discussion. Propagate the input collation to all collatable input parameters. I chose to also propagate the input collation to all declared variables of collatable types, which is a bit more debatable but seems to be necessary for non-astonishing behavior. (Copying a parameter into a separate local variable shouldn't result in a change of behavior, for example.) There is enough infrastructure here to support declaring a collation for each local variable to override that default, but I thought we should wait to see what the field demand is before adding such a feature. In passing, remove exec_get_rec_fieldtype(), which wasn't used anywhere. Documentation patch to follow.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-08 17:28:27 +0000