aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Split the LDFLAGS make variable into two parts: LDFLAGS is now used forTom Lane2010-07-05
| | | | | | | | | | | | | linking both executables and shared libraries, and we add on LDFLAGS_EX when linking executables or LDFLAGS_SL when linking shared libraries. This provides a significantly cleaner way of dealing with link-time switches than the former behavior. Also, make sure that the various platform-specific %.so: %.o rules incorporate LDFLAGS and LDFLAGS_SL; most of them missed that before. (I did not add these variables for the platforms that invoke $(LD) directly, however. It's not clear if we can do that safely, since for the most part we assume these variables use CC command-line syntax.) Per gripe from Aaron Swenson and subsequent investigation.
* The previous fix in CVS HEAD and 8.4 for handling the case where a cursorHeikki Linnakangas2010-07-05
| | | | | | | | | | | being used in a PL/pgSQL FOR loop is closed was inadequate, as Tom Lane pointed out. The bug affects FOR statement variants too, because you can close an implicitly created cursor too by guessing the "<unnamed portal X>" name created for it. To fix that, "pin" the portal to prevent it from being dropped while it's being used in a PL/pgSQL FOR loop. Backpatch all the way to 7.4 which is the oldest supported version.
* Simplify test_fsync duration computation.Bruce Momjian2010-07-04
|
* Report test_fynsc times in tests per second, instead of total seconds.Bruce Momjian2010-07-04
|
* Remove SGML tab.Bruce Momjian2010-07-03
|
* Don't set recoveryLastXTime when replaying a checkpoint --- that was a bogusTom Lane2010-07-03
| | | | | | | | idea from the start since the variable is only meant to track commit/abort events. This patch reverts the logic around the variable to what it was in 8.4, except that the value is now kept in shared memory rather than a static variable, so that it can be reported correctly by CreateRestartPoint (which is executed in the bgwriter).
* Make vacuum_defer_cleanup_age be PGC_SIGHUP level, since it's not sensibleTom Lane2010-07-03
| | | | | | | to have different values in different processes of the primary server. Also put it into the "Streaming Replication" GUC category; it doesn't belong in "Standby Servers" because you use it on the master not the standby. In passing also correct guc.c's idea of wal_keep_segments' category.
* Replace max_standby_delay with two parameters, max_standby_archive_delay andTom Lane2010-07-03
| | | | | | | | | | | | | | max_standby_streaming_delay, and revise the implementation to avoid assuming that timestamps found in WAL records can meaningfully be compared to clock time on the standby server. Instead, the delay limits are compared to the elapsed time since we last obtained a new WAL segment from archive or since we were last "caught up" to WAL data arriving via streaming replication. This avoids problems with clock skew between primary and standby, as well as other corner cases that the original coding would misbehave in, such as the primary server having significant idle time between transactions. Per my complaint some time ago and considerable ensuing discussion. Do some desultory editing on the hot standby documentation, too.
* Document more clearly on XML namespaces inside xpath functionBruce Momjian2010-07-03
| | | | Nikolay Samokhvalov
* Make pg_upgrade copyrights just 2010, not 2010-2010.Bruce Momjian2010-07-03
|
* Add copyrights to pg_upgrade and pg_upgrade_tools files, per Tom.Bruce Momjian2010-07-03
|
* Add CVS tags to pg_upgrade and pg_upgrade_support files, per requestBruce Momjian2010-07-03
| | | | from Tom.
* Allow REASSIGNED OWNED to handle opclasses and opfamilies.Robert Haas2010-07-03
| | | | | | | | Backpatch to 8.3, which is as far back as we have opfamilies. The opclass portion could probably be backpatched to 8.2, when REASSIGN OWNED was added, but for now I have not done that. Asko Tiidumaa, with minor adjustments by me.
* Fix assorted misstatements and poor wording in the descriptions of the I/OTom Lane2010-07-03
| | | | | | | | | formats for geometric types. Per bug #5536 from Jon Strait, and my own testing. Back-patch to all supported branches, since this doco has been wrong right along -- we certainly haven't changed the I/O behavior of these types in many years.
* Additional cross-references to window functions documentation.Robert Haas2010-07-03
| | | | Erik Rijkers
* Unbreak MSVC builds by removing copydir.c from list of libpgport filesAndrew Dunstan2010-07-02
|
* Remove hstore % text[] operator; use slice() function instead.Robert Haas2010-07-02
| | | | David Wheeler, with one small correction by me.
* Move copydir.c from src/port to src/backend/storage/fileRobert Haas2010-07-02
| | | | | | | | | | | | | The previous commit to make copydir() interruptible prevented postgres.exe from linking on MinGW and Cygwin, because on those platforms libpgport_srv.a can't freely reference symbols defined by the backend. Since that code is already backend-specific anyway, just move the whole file into the backend rather than adding further kludges to deal with the symbols needed by CHECK_FOR_INTERRUPTS(). This probably needs some further cleanup, but this commit just moves the file as-is, which should hopefully be enough to turn the buildfarm green again.
* Issue 'mkdir' hint when replying CREATE TABLESPACE in recovery mode.Bruce Momjian2010-07-02
| | | | Per idea from Fujii Masao
* Allow copydir() to be interrupted.Robert Haas2010-07-01
| | | | | | | | | This makes ALTER DATABASE .. SET TABLESPACE and CREATE DATABASE more sensitive to interrupts. Backpatch to 8.4, where ALTER DATABASE .. SET TABLESPACE was introduced. We could go back further, but in the absence of complaints about the CREATE DATABASE case it doesn't seem worth it. Guillaume Lelarge, with a small correction by me.
* Get rid of some more stuff that duplicates c.h or port.h.Tom Lane2010-07-01
|
* Remove port.h prototypes from pg_upgrade.h, per report from Robert Haas.Bruce Momjian2010-07-01
|
* Allow ALTER TABLE .. SET TABLESPACE to be interrupted.Robert Haas2010-07-01
| | | | | | Backpatch to 8.0, where tablespaces were introduced. Guillaume Lelarge
* Update 9.0 release notes so streaming replication and hot standby is notBruce Momjian2010-07-01
| | | | | | assumed to require continuous archiving. Per report from Fujii Masao
* stringToNode() and deparse_expression_pretty() crash on invalid input,Heikki Linnakangas2010-06-30
| | | | | | | | | | but we have nevertheless exposed them to users via pg_get_expr(). It would be too much maintenance effort to rigorously check the input, so put a hack in place instead to restrict pg_get_expr() so that the argument must come from one of the system catalog columns known to contain valid expressions. Per report from Rushabh Lathia. Backpatch to 7.4 which is the oldest supported version at the moment.
* Correct missing/misspelled surname.Andrew Dunstan2010-06-30
|
* Document that /bin/true on Windows is implemented by 'REM'.Bruce Momjian2010-06-30
|
* In documentation, use "lower case"/"upper case" consistently (use spaceBruce Momjian2010-06-29
| | | | between words).
* Document that shared_preload_libraries and local_preload_librariesBruce Momjian2010-06-29
| | | | lowercase the library names, unless double-quoted.
* Add compatibility note warning that plpgsql is now stricter about the columnTom Lane2010-06-29
| | | | | datatypes of composite results, per gripe from Marcel Asio. Some desultory copy-editing of plpgsql-related sections of the release notes.
* Add C comment about why synchronous_commit=off behavior can loseBruce Momjian2010-06-29
| | | | committed transactions in a postmaster crash.
* Message tuningPeter Eisentraut2010-06-29
|
* Use different function names for plpython3 handlers, to avoid clashes inPeter Eisentraut2010-06-29
| | | | | | | pg_pltemplate This should have a catversion bump, but it's still being debated whether it's worth it during beta.
* Add note clarifying that XML fragments don't accept DTDsPeter Eisentraut2010-06-29
| | | | per complaint from Craig Ringer
* Fix doc double-wording in non-durable patch.Bruce Momjian2010-06-28
| | | | Report from Thom Brown
* Add new Non-Durable Settings documentation section.Bruce Momjian2010-06-28
| | | | | Document that synchronous_commit can lose transactions in a db crash, not just a OS crash.
* emode_for_corrupt_record shouldn't reduce LOG messages to WARNING.Robert Haas2010-06-28
| | | | In non-interactive sessions, WARNING sorts below LOG.
* Add guidelines for formatting errcontext stringsPeter Eisentraut2010-06-28
|
* Remove tab from SGML.Bruce Momjian2010-06-28
|
* Improve pg_dump's checkSeek() function to verify the functioning of ftelloTom Lane2010-06-28
| | | | | | | | | | as well as fseeko, and to not assume that fseeko(fp, 0, SEEK_CUR) proves anything. Also improve some related comments. Per my observation that the SEEK_CUR test didn't actually work on some platforms, and subsequent discussion with Robert Haas. Back-patch to 8.4. In earlier releases it's not that important whether we get the hasSeek test right, but with parallel restore it matters.
* Fix pg_restore so parallel restore doesn't fail when the input file doesn'tTom Lane2010-06-27
| | | | | | | | | | contain data offsets (which it won't, if pg_dump thought its output wasn't seekable). To do that, remove an unnecessarily aggressive error check, and instead fail if we get to the end of the archive without finding the desired data item. Also improve the error message to be more specific about the cause of the problem. Per discussion of recent report from Igor Neyman. Back-patch to 8.4 where parallel restore was introduced.
* Rewrite docs for new libpq keepalive parameters.Robert Haas2010-06-25
| | | | | | | The revised documentation makes it more clear that these are client-side parameters, rather than server side parameters. It also puts the main point of each parameter first, and consolidates the conditions under which it might be ignored in a single list at the end.
* Make AIX suggestions about disabling ipv6 more version-sensitive.Robert Haas2010-06-25
| | | | Chris Browne, based on a report from John Pierce.
* Fix thinko in tok_is_keyword(): it was looking at the wrong union variantTom Lane2010-06-25
| | | | | | of YYSTYPE, and hence returning the wrong answer for cases where a plpgsql "unreserved keyword" really does conflict with a variable name. Obviously I didn't test this enough :-(. Per bug #5524 from Peter Gagarinov.
* Fix log_temp_files docs and comments to say bytes not kilobytes.Simon Riggs2010-06-25
| | | | | stat(2) field st_size returns bytes not kilobytes. Bug found during recent performance tuning for PostgreSQL user.
* Some copy-editing of the Hot Standby documentation.Robert Haas2010-06-24
| | | | Thanks to Joshua Tolley for the review.
* Further 9.0 release notes updates.Robert Haas2010-06-24
| | | | Josh Berkus
* Add stray "else" that seems to have gone missing.Robert Haas2010-06-24
|
* Mention that when alter rewrites a table, indexes are also rebuilt.Bruce Momjian2010-06-24
|
* Add TCP keepalive support to libpq.Robert Haas2010-06-23
| | | | | | | | | | | | | | | | This adds four additional connection parameters to libpq: keepalives, keepalives_idle, keepalives_count, and keepalives_interval. keepalives default to on, per discussion, but can be turned off by specifying keepalives=0. The remaining parameters, where supported, can be used to adjust how often keepalives are sent and how many can be lost before the connection is broken. The immediate motivation for this patch is to make sure that walreceiver will eventually notice if the master reboots without closing the connection cleanly, but it should be helpful in other cases as well. Tollef Fog Heen, Fujii Masao, and me.