diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml
index 0bff9e6ebc7..5762e01f621 100644
--- a/doc/src/sgml/release-8.4.sgml
+++ b/doc/src/sgml/release-8.4.sgml
@@ -1,6 +1,207 @@
+
+ Release 8.4.19
+
+
+ Release Date
+ 2013-12-05
+
+
+
+ This release contains a variety of fixes from 8.4.18.
+ For information about new features in the 8.4 major release, see
+ .
+
+
+
+ Migration to Version 8.4.19
+
+
+ A dump/restore is not required for those running 8.4.X.
+
+
+
+ However, this release corrects a potential data corruption
+ issue. See the first changelog entry below to find out whether
+ your installation has been affected and what steps you can take if so.
+
+
+
+ Also, if you are upgrading from a version earlier than 8.4.17,
+ see the release notes for 8.4.17.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
+
+
+
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid value,
+ allowing tuples to escape freezing, causing those rows to become
+ invisible once 2^31 transactions have elapsed. The probability of
+ data loss is fairly low since multiple incorrect advancements would
+ need to happen before actual loss occurs, but it's not zero. Users
+ upgrading from release 8.4.8 or earlier are not affected, but all later
+ versions contain the bug.
+
+
+
+ The issue can be ameliorated by, after upgrading, vacuuming all tables
+ in all databases while having vacuum_freeze_table_age
+ set to zero. This will fix any latent corruption but will not be able
+ to fix all pre-existing data errors. However, an installation can be
+ presumed safe after performing this vacuuming if it has executed fewer
+ than 2^31 update transactions in its lifetime (check this with
+ SELECT txid_current() < 2^31).
+
+
+
+
+
+ Fix race condition in GIN index posting tree page deletion (Heikki
+ Linnakangas)
+
+
+
+ This could lead to transient wrong answers or query failures.
+
+
+
+
+
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
+
+
+
+ This avoids unexpected results due to extra evaluations of the
+ volatile function.
+
+
+
+
+
+ Fix planner's processing of non-simple-variable subquery outputs
+ nested within outer joins (Tom Lane)
+
+
+
+ This error could lead to incorrect plans for queries involving
+ multiple levels of subqueries within JOIN syntax.
+
+
+
+
+
+ Fix premature deletion of temporary files (Andres Freund)
+
+
+
+
+
+ Fix possible read past end of memory in rule printing (Peter Eisentraut)
+
+
+
+
+
+ Fix array slicing of int2vector and oidvector values
+ (Tom Lane)
+
+
+
+ Expressions of this kind are now implicitly promoted to
+ regular int2 or oid arrays.
+
+
+
+
+
+ Fix incorrect behaviors when using a SQL-standard, simple GMT offset
+ timezone (Tom Lane)
+
+
+
+ In some cases, the system would use the simple GMT offset value when
+ it should have used the regular timezone setting that had prevailed
+ before the simple offset was selected. This change also causes
+ the timeofday function to honor the simple GMT offset
+ zone.
+
+
+
+
+
+ Prevent possible misbehavior when logging translations of Windows
+ error codes (Tom Lane)
+
+
+
+
+
+ Properly quote generated command lines in pg_ctl
+ (Naoya Anzai and Tom Lane)
+
+
+
+ This fix applies only to Windows.
+
+
+
+
+
+ Fix pg_dumpall to work when a source database
+ sets default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
+
+
+
+ Previously, the generated script would fail during restore.
+
+
+
+
+
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
+
+
+
+
+
+ Make contrib/lo defend against incorrect trigger definitions
+ (Marc Cousin)
+
+
+
+
+
+ Update time zone data files to tzdata release 2013h
+ for DST law changes in Argentina, Brazil, Jordan, Libya,
+ Liechtenstein, Morocco, and Palestine. Also, new timezone
+ abbreviations WIB, WIT, WITA for Indonesia.
+
+
+
+
+
+
+
+
Release 8.4.18
diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index ca1d7d8c70e..6dc1f6976dd 100644
--- a/doc/src/sgml/release-9.0.sgml
+++ b/doc/src/sgml/release-9.0.sgml
@@ -1,6 +1,244 @@
+
+ Release 9.0.15
+
+
+ Release Date
+ 2013-12-05
+
+
+
+ This release contains a variety of fixes from 9.0.14.
+ For information about new features in the 9.0 major release, see
+ .
+
+
+
+ Migration to Version 9.0.15
+
+
+ A dump/restore is not required for those running 9.0.X.
+
+
+
+ However, this release corrects a number of potential data corruption
+ issues. See the first two changelog entries below to find out whether
+ your installation has been affected and what steps you can take if so.
+
+
+
+ Also, if you are upgrading from a version earlier than 9.0.13,
+ see the release notes for 9.0.13.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
+
+
+
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid value,
+ allowing tuples to escape freezing, causing those rows to become
+ invisible once 2^31 transactions have elapsed. The probability of
+ data loss is fairly low since multiple incorrect advancements would
+ need to happen before actual loss occurs, but it's not zero. Users
+ upgrading from releases 9.0.4 or 8.4.8 or earlier are not affected, but
+ all later versions contain the bug.
+
+
+
+ The issue can be ameliorated by, after upgrading, vacuuming all tables
+ in all databases while having vacuum_freeze_table_age
+ set to zero. This will fix any latent corruption but will not be able
+ to fix all pre-existing data errors. However, an installation can be
+ presumed safe after performing this vacuuming if it has executed fewer
+ than 2^31 update transactions in its lifetime (check this with
+ SELECT txid_current() < 2^31).
+
+
+
+
+
+ Fix initialization of pg_clog and pg_subtrans
+ during hot standby startup (Andres Freund, Heikki Linnakangas)
+
+
+
+ This bug can cause data loss on standby servers at the moment they
+ start to accept hot-standby queries, by marking committed transactions
+ as uncommitted. The likelihood of such corruption is small unless, at
+ the time of standby startup, the primary server has executed many
+ updating transactions since its last checkpoint. Symptoms include
+ missing rows, rows that should have been deleted being still visible,
+ and obsolete versions of updated rows being still visible alongside
+ their newer versions.
+
+
+
+ This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and 9.0.14.
+ Standby servers that have only been running earlier releases are not
+ at risk. It's recommended that standby servers that have ever run any
+ of the buggy releases be re-cloned from the primary (e.g., with a new
+ base backup) after upgrading.
+
+
+
+
+
+ Truncate pg_multixact contents during WAL replay
+ (Andres Freund)
+
+
+
+ This avoids ever-increasing disk space consumption in standby servers.
+
+
+
+
+
+ Fix race condition in GIN index posting tree page deletion (Heikki
+ Linnakangas)
+
+
+
+ This could lead to transient wrong answers or query failures.
+
+
+
+
+
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
+
+
+
+ This avoids unexpected results due to extra evaluations of the
+ volatile function.
+
+
+
+
+
+ Fix planner's processing of non-simple-variable subquery outputs
+ nested within outer joins (Tom Lane)
+
+
+
+ This error could lead to incorrect plans for queries involving
+ multiple levels of subqueries within JOIN syntax.
+
+
+
+
+
+ Fix premature deletion of temporary files (Andres Freund)
+
+
+
+
+
+ Fix possible read past end of memory in rule printing (Peter Eisentraut)
+
+
+
+
+
+ Fix array slicing of int2vector and oidvector values
+ (Tom Lane)
+
+
+
+ Expressions of this kind are now implicitly promoted to
+ regular int2 or oid arrays.
+
+
+
+
+
+ Fix incorrect behaviors when using a SQL-standard, simple GMT offset
+ timezone (Tom Lane)
+
+
+
+ In some cases, the system would use the simple GMT offset value when
+ it should have used the regular timezone setting that had prevailed
+ before the simple offset was selected. This change also causes
+ the timeofday function to honor the simple GMT offset
+ zone.
+
+
+
+
+
+ Prevent possible misbehavior when logging translations of Windows
+ error codes (Tom Lane)
+
+
+
+
+
+ Properly quote generated command lines in pg_ctl
+ (Naoya Anzai and Tom Lane)
+
+
+
+ This fix applies only to Windows.
+
+
+
+
+
+ Fix pg_dumpall to work when a source database
+ sets default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
+
+
+
+ Previously, the generated script would fail during restore.
+
+
+
+
+
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
+
+
+
+
+
+ Make contrib/lo defend against incorrect trigger definitions
+ (Marc Cousin)
+
+
+
+
+
+ Update time zone data files to tzdata release 2013h
+ for DST law changes in Argentina, Brazil, Jordan, Libya,
+ Liechtenstein, Morocco, and Palestine. Also, new timezone
+ abbreviations WIB, WIT, WITA for Indonesia.
+
+
+
+
+
+
+
+
Release 9.0.14
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml
index 577b9b852e6..b3f5c522727 100644
--- a/doc/src/sgml/release-9.1.sgml
+++ b/doc/src/sgml/release-9.1.sgml
@@ -1,6 +1,263 @@
+
+ Release 9.1.11
+
+
+ Release Date
+ 2013-12-05
+
+
+
+ This release contains a variety of fixes from 9.1.10.
+ For information about new features in the 9.1 major release, see
+ .
+
+
+
+ Migration to Version 9.1.11
+
+
+ A dump/restore is not required for those running 9.1.X.
+
+
+
+ However, this release corrects a number of potential data corruption
+ issues. See the first two changelog entries below to find out whether
+ your installation has been affected and what steps you can take if so.
+
+
+
+ Also, if you are upgrading from a version earlier than 9.1.9,
+ see the release notes for 9.1.9.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
+
+
+
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid value,
+ allowing tuples to escape freezing, causing those rows to become
+ invisible once 2^31 transactions have elapsed. The probability of
+ data loss is fairly low since multiple incorrect advancements would
+ need to happen before actual loss occurs, but it's not zero. Users
+ upgrading from releases 9.0.4 or 8.4.8 or earlier are not affected, but
+ all later versions contain the bug.
+
+
+
+ The issue can be ameliorated by, after upgrading, vacuuming all tables
+ in all databases while having vacuum_freeze_table_age
+ set to zero. This will fix any latent corruption but will not be able
+ to fix all pre-existing data errors. However, an installation can be
+ presumed safe after performing this vacuuming if it has executed fewer
+ than 2^31 update transactions in its lifetime (check this with
+ SELECT txid_current() < 2^31).
+
+
+
+
+
+ Fix initialization of pg_clog and pg_subtrans
+ during hot standby startup (Andres Freund, Heikki Linnakangas)
+
+
+
+ This bug can cause data loss on standby servers at the moment they
+ start to accept hot-standby queries, by marking committed transactions
+ as uncommitted. The likelihood of such corruption is small unless, at
+ the time of standby startup, the primary server has executed many
+ updating transactions since its last checkpoint. Symptoms include
+ missing rows, rows that should have been deleted being still visible,
+ and obsolete versions of updated rows being still visible alongside
+ their newer versions.
+
+
+
+ This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and 9.0.14.
+ Standby servers that have only been running earlier releases are not
+ at risk. It's recommended that standby servers that have ever run any
+ of the buggy releases be re-cloned from the primary (e.g., with a new
+ base backup) after upgrading.
+
+
+
+
+
+ Truncate pg_multixact contents during WAL replay
+ (Andres Freund)
+
+
+
+ This avoids ever-increasing disk space consumption in standby servers.
+
+
+
+
+
+ Fix race condition in GIN index posting tree page deletion (Heikki
+ Linnakangas)
+
+
+
+ This could lead to transient wrong answers or query failures.
+
+
+
+
+
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
+
+
+
+ This avoids unexpected results due to extra evaluations of the
+ volatile function.
+
+
+
+
+
+ Fix planner's processing of non-simple-variable subquery outputs
+ nested within outer joins (Tom Lane)
+
+
+
+ This error could lead to incorrect plans for queries involving
+ multiple levels of subqueries within JOIN syntax.
+
+
+
+
+
+ Fix incorrect generation of optimized MIN()/MAX() plans for
+ inheritance trees (Tom Lane)
+
+
+
+ The planner could fail in cases where the MIN()/MAX() argument was an
+ expression rather than a simple variable.
+
+
+
+
+
+ Fix premature deletion of temporary files (Andres Freund)
+
+
+
+
+
+ Fix possible read past end of memory in rule printing (Peter Eisentraut)
+
+
+
+
+
+ Fix array slicing of int2vector and oidvector values
+ (Tom Lane)
+
+
+
+ Expressions of this kind are now implicitly promoted to
+ regular int2 or oid arrays.
+
+
+
+
+
+ Fix incorrect behaviors when using a SQL-standard, simple GMT offset
+ timezone (Tom Lane)
+
+
+
+ In some cases, the system would use the simple GMT offset value when
+ it should have used the regular timezone setting that had prevailed
+ before the simple offset was selected. This change also causes
+ the timeofday function to honor the simple GMT offset
+ zone.
+
+
+
+
+
+ Prevent possible misbehavior when logging translations of Windows
+ error codes (Tom Lane)
+
+
+
+
+
+ Properly quote generated command lines in pg_ctl
+ (Naoya Anzai and Tom Lane)
+
+
+
+ This fix applies only to Windows.
+
+
+
+
+
+ Fix pg_dumpall to work when a source database
+ sets default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
+
+
+
+ Previously, the generated script would fail during restore.
+
+
+
+
+
+ Make ecpg search for quoted cursor names
+ case-sensitively (Zoltán Böszörményi)
+
+
+
+
+
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
+
+
+
+
+
+ Make contrib/lo defend against incorrect trigger definitions
+ (Marc Cousin)
+
+
+
+
+
+ Update time zone data files to tzdata release 2013h
+ for DST law changes in Argentina, Brazil, Jordan, Libya,
+ Liechtenstein, Morocco, and Palestine. Also, new timezone
+ abbreviations WIB, WIT, WITA for Indonesia.
+
+
+
+
+
+
+
+
Release 9.1.10
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 034e580ded6..b373e33f1e5 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -1,6 +1,343 @@
+
+ Release 9.2.6
+
+
+ Release Date
+ 2013-12-05
+
+
+
+ This release contains a variety of fixes from 9.2.5.
+ For information about new features in the 9.2 major release, see
+ .
+
+
+
+ Migration to Version 9.2.6
+
+
+ A dump/restore is not required for those running 9.2.X.
+
+
+
+ However, this release corrects a number of potential data corruption
+ issues. See the first two changelog entries below to find out whether
+ your installation has been affected and what steps you can take if so.
+
+
+
+ Also, if you are upgrading from a version earlier than 9.2.4,
+ see the release notes for 9.2.4.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Fix VACUUM's tests to see whether it can
+ update relfrozenxid (Andres Freund)
+
+
+
+ In some cases VACUUM (either manual or autovacuum) could
+ incorrectly advance a table's relfrozenxid value,
+ allowing tuples to escape freezing, causing those rows to become
+ invisible once 2^31 transactions have elapsed. The probability of
+ data loss is fairly low since multiple incorrect advancements would
+ need to happen before actual loss occurs, but it's not zero. In 9.2.0
+ and later, the probability of loss is higher, and it's also possible
+ to get could not access status of transaction errors as a
+ consequence of this bug. Users upgrading from releases 9.0.4 or 8.4.8
+ or earlier are not affected, but all later versions contain the bug.
+
+
+
+ The issue can be ameliorated by, after upgrading, vacuuming all tables
+ in all databases while having vacuum_freeze_table_age
+ set to zero. This will fix any latent corruption but will not be able
+ to fix all pre-existing data errors. However, an installation can be
+ presumed safe after performing this vacuuming if it has executed fewer
+ than 2^31 update transactions in its lifetime (check this with
+ SELECT txid_current() < 2^31).
+
+
+
+
+
+ Fix initialization of pg_clog and pg_subtrans
+ during hot standby startup (Andres Freund, Heikki Linnakangas)
+
+
+
+ This bug can cause data loss on standby servers at the moment they
+ start to accept hot-standby queries, by marking committed transactions
+ as uncommitted. The likelihood of such corruption is small unless, at
+ the time of standby startup, the primary server has executed many
+ updating transactions since its last checkpoint. Symptoms include
+ missing rows, rows that should have been deleted being still visible,
+ and obsolete versions of updated rows being still visible alongside
+ their newer versions.
+
+
+
+ This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and 9.0.14.
+ Standby servers that have only been running earlier releases are not
+ at risk. It's recommended that standby servers that have ever run any
+ of the buggy releases be re-cloned from the primary (e.g., with a new
+ base backup) after upgrading.
+
+
+
+
+
+ Fix dangling-pointer problem in fast-path locking (Tom Lane)
+
+
+
+ This could lead to corruption of the lock data structures in shared
+ memory, causing lock already held and other odd errors.
+
+
+
+
+
+ Truncate pg_multixact contents during WAL replay
+ (Andres Freund)
+
+
+
+ This avoids ever-increasing disk space consumption in standby servers.
+
+
+
+
+
+ Ensure an anti-wraparound VACUUM counts a page as scanned
+ when it's only verified that no tuples need freezing (Sergey
+ Burladyan, Jeff Janes)
+
+
+
+ This bug could result in failing to
+ advance relfrozenxid, so that the table would still be
+ thought to need another anti-wraparound vacuum. In the worst case the
+ database might even shut down to prevent wraparound.
+
+
+
+
+
+ Fix race condition in GIN index posting tree page deletion (Heikki
+ Linnakangas)
+
+
+
+ This could lead to transient wrong answers or query failures.
+
+
+
+
+
+ Fix unexpected spgdoinsert() failure error during SP-GiST
+ index creation (Teodor Sigaev)
+
+
+
+
+
+ Avoid flattening a subquery whose SELECT list contains a
+ volatile function wrapped inside a sub-SELECT (Tom Lane)
+
+
+
+ This avoids unexpected results due to extra evaluations of the
+ volatile function.
+
+
+
+
+
+ Fix planner's processing of non-simple-variable subquery outputs
+ nested within outer joins (Tom Lane)
+
+
+
+ This error could lead to incorrect plans for queries involving
+ multiple levels of subqueries within JOIN syntax.
+
+
+
+
+
+ Fix incorrect planning in cases where the same non-strict expression
+ appears in multiple WHERE and outer JOIN
+ equality clauses (Tom Lane)
+
+
+
+
+
+ Fix planner crash with whole-row reference to a subquery (Tom Lane)
+
+
+
+
+
+ Fix incorrect generation of optimized MIN()/MAX() plans for
+ inheritance trees (Tom Lane)
+
+
+
+ The planner could fail in cases where the MIN()/MAX() argument was an
+ expression rather than a simple variable.
+
+
+
+
+
+ Fix premature deletion of temporary files (Andres Freund)
+
+
+
+
+
+ Prevent intra-transaction memory leak when printing range values
+ (Tom Lane)
+
+
+
+ This fix actually cures transient memory leaks in any datatype output
+ function, but range types are the only ones known to have had a
+ significant problem.
+
+
+
+
+
+ Prevent incorrect display of dropped columns in NOT NULL and CHECK
+ constraint violation messages (Michael Paquier and Tom Lane)
+
+
+
+
+
+ Allow default arguments and named-argument notation for window
+ functions (Tom Lane)
+
+
+
+ Previously, these cases were likely to crash.
+
+
+
+
+
+ Fix possible read past end of memory in rule printing (Peter Eisentraut)
+
+
+
+
+
+ Fix array slicing of int2vector and oidvector values
+ (Tom Lane)
+
+
+
+ Expressions of this kind are now implicitly promoted to
+ regular int2 or oid arrays.
+
+
+
+
+
+ Fix incorrect behaviors when using a SQL-standard, simple GMT offset
+ timezone (Tom Lane)
+
+
+
+ In some cases, the system would use the simple GMT offset value when
+ it should have used the regular timezone setting that had prevailed
+ before the simple offset was selected. This change also causes
+ the timeofday function to honor the simple GMT offset
+ zone.
+
+
+
+
+
+ Prevent possible misbehavior when logging translations of Windows
+ error codes (Tom Lane)
+
+
+
+
+
+ Properly quote generated command lines in pg_ctl
+ (Naoya Anzai and Tom Lane)
+
+
+
+ This fix applies only to Windows.
+
+
+
+
+
+ Fix pg_dumpall to work when a source database
+ sets default_transaction_read_only
+ via ALTER DATABASE SET (Kevin Grittner)
+
+
+
+ Previously, the generated script would fail during restore.
+
+
+
+
+
+ Make ecpg search for quoted cursor names
+ case-sensitively (Zoltán Böszörményi)
+
+
+
+
+
+ Fix ecpg's processing of lists of variables
+ declared varchar (Zoltán Böszörményi)
+
+
+
+
+
+ Make contrib/lo defend against incorrect trigger definitions
+ (Marc Cousin)
+
+
+
+
+
+ Update time zone data files to tzdata release 2013h
+ for DST law changes in Argentina, Brazil, Jordan, Libya,
+ Liechtenstein, Morocco, and Palestine. Also, new timezone
+ abbreviations WIB, WIT, WITA for Indonesia.
+
+
+
+
+
+
+
+
Release 9.2.5
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index c72ac85a8fd..68e8eb7fbf4 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -40,16 +40,6 @@
-
-
Fix VACUUM's tests to see whether it can
@@ -81,12 +71,6 @@ Branch: REL8_4_STABLE [8a7f4466a] 2013-11-27 13:40:05 +0200
-
-
Fix multiple bugs in MultiXactId freezing (Andres Freund,
@@ -116,15 +100,6 @@ Branch: REL9_3_STABLE [8e53ae025] 2013-11-29 21:48:21 -0300
-
-
Fix initialization of pg_clog and pg_subtrans
@@ -151,12 +126,6 @@ Branch: REL9_0_STABLE [b4f697f8e] 2013-11-22 14:49:07 +0200
-
-
Fix multiple bugs in update chain traversal (Andres Freund,
@@ -171,13 +140,6 @@ Branch: REL9_3_STABLE [663d2e485] 2013-11-29 21:48:18 -0300
-
-
Fix dangling-pointer problem in fast-path locking (Tom Lane)
@@ -189,12 +151,6 @@ Branch: REL9_2_STABLE [024edb454] 2013-11-27 18:10:06 -0500
-
-
Fix assorted race conditions in timeout management (Tom Lane)
@@ -206,15 +162,6 @@ Branch: REL9_3_STABLE [c357be2cd] 2013-11-29 16:41:03 -0500
-
-
Truncate pg_multixact contents during WAL replay
@@ -226,13 +173,6 @@ Branch: REL9_0_STABLE [6d0b8cd2f] 2013-11-29 22:02:15 -0300
-
-
Ensure an anti-wraparound VACUUM counts a page as scanned
@@ -248,12 +188,6 @@ Branch: REL9_2_STABLE [3379263b6] 2013-11-18 10:12:22 +0200
-
-
Fix full-table-vacuum request mechanism for MultiXactIds (Andres Freund)
@@ -264,16 +198,6 @@ Branch: REL9_3_STABLE [f5f92bdc4] 2013-11-29 21:48:11 -0300
-
-
Fix race condition in GIN index posting tree page deletion (Heikki
@@ -285,13 +209,6 @@ Branch: REL8_4_STABLE [b6f82acef] 2013-11-08 22:23:19 +0200
-
-
Fix unexpected spgdoinsert() failure error during SP-GiST
@@ -299,24 +216,12 @@ Branch: REL9_2_STABLE [a1c3d54fb] 2013-11-02 16:45:57 -0400
-
-
Fix assorted bugs in materialized views (Kevin Grittner, Andres Freund)
-
-
Re-allow duplicate table aliases if they're within aliased JOINs
@@ -335,16 +240,6 @@ SELECT ... FROM tab1 x CROSS JOIN (tab2 x CROSS JOIN tab3 y) z
-
-
Avoid flattening a subquery whose SELECT list contains a
@@ -357,16 +252,6 @@ Branch: REL8_4_STABLE [90b07dd7b] 2013-11-08 11:37:17 -0500
-
-
Fix planner's processing of non-simple-variable subquery outputs
@@ -379,13 +264,6 @@ Branch: REL8_4_STABLE [122ba5dad] 2013-11-22 14:37:38 -0500
-
-
Fix incorrect planning in cases where the same non-strict expression
@@ -394,27 +272,12 @@ Branch: REL9_2_STABLE [51b6ae6bb] 2013-11-15 16:46:25 -0500
-
-
Fix planner crash with whole-row reference to a subquery (Tom Lane)
-
-
Fix incorrect generation of optimized MIN()/MAX() plans for
@@ -427,29 +290,12 @@ Branch: REL9_1_STABLE [6e2c76248] 2013-11-07 13:13:47 -0500
-
-
Fix premature deletion of temporary files (Andres Freund)
-
-
Prevent intra-transaction memory leak when printing range values
@@ -463,12 +309,6 @@ Branch: REL9_2_STABLE [85de12624] 2013-11-03 11:33:13 -0500
-
-
Fix memory leaks when reloading configuration files (Heikki
@@ -476,13 +316,6 @@ Branch: REL9_3_STABLE [bb604d03a] 2013-10-24 15:28:15 +0300
-
-
Prevent incorrect display of dropped columns in NOT NULL and CHECK
@@ -490,13 +323,6 @@ Branch: REL9_2_STABLE [8bd5a6af6] 2013-11-07 14:41:43 -0500
-
-
Allow default arguments and named-argument notation for window
@@ -508,12 +334,6 @@ Branch: REL9_2_STABLE [74aea2af9] 2013-11-06 13:26:38 -0500
-
-
Suppress trailing whitespace on each line when pretty-printing rules
@@ -527,32 +347,12 @@ Branch: REL9_3_STABLE [fbbd150a2] 2013-11-11 13:36:42 -0500
-
-
Fix possible read past end of memory in rule printing (Peter Eisentraut)
-
-
Fix array slicing of int2vector and oidvector values
@@ -565,12 +365,6 @@ Branch: REL8_4_STABLE [d0378c8a8] 2013-11-23 20:04:13 -0500
-
-
Return a valid JSON value when converting an empty hstore value
@@ -579,16 +373,6 @@ Branch: REL9_3_STABLE [bfb327ac1] 2013-10-17 11:09:55 -0400
-
-
Fix incorrect behaviors when using a SQL-standard, simple GMT offset
@@ -604,16 +388,6 @@ Branch: REL8_4_STABLE [01499ea33] 2013-11-01 12:13:38 -0400
-
-
Prevent possible misbehavior when logging translations of Windows
@@ -621,16 +395,6 @@ Branch: REL8_4_STABLE [3482f2986] 2013-11-23 18:25:00 -0500
-
-
Properly quote generated command lines in pg_ctl
@@ -642,16 +406,6 @@ Branch: REL8_4_STABLE [6cb109a81] 2013-11-29 18:34:25 -0500
-
-
Fix pg_dumpall to work when a source database
@@ -665,12 +419,6 @@ Branch: REL8_4_STABLE [ac7113bb3] 2013-11-30 12:07:18 -0600
-
-
Fix pg_isready to handle its
-
+
+
+ Fix parsing of WAL file names in pg_receivexlog
+ (Heikki Linnakangas)
+
+
+
+ This error made pg_receivexlog unable to restart
+ streaming after stopping, once at least 4 GB of WAL had been written.
+
+
@@ -691,14 +445,6 @@ Branch: REL9_3_STABLE [8ca75671b] 2013-11-18 22:02:36 -0500
-
-
Make ecpg search for quoted cursor names
@@ -706,16 +452,6 @@ Branch: REL9_1_STABLE [9a1c6dd43] 2013-11-27 11:15:34 +0100
-
-
Fix ecpg's processing of lists of variables
@@ -723,16 +459,6 @@ Branch: REL8_4_STABLE [3b41a7c74] 2013-11-26 17:30:24 +0100
-
-
Make contrib/lo defend against incorrect trigger definitions
@@ -740,16 +466,6 @@ Branch: REL8_4_STABLE [2c3b7d224] 2013-11-23 22:46:21 -0500
-
-
Update time zone data files to tzdata release 2013h