From 0dfbad834ffe8f828cbb05d63f744be9cd7d0ab6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 1 Apr 2013 14:11:16 -0400 Subject: [PATCH] Update release notes for 9.2.4, 9.1.9, 9.0.13, 8.4.17. Security: CVE-2013-1899, CVE-2013-1901 --- doc/src/sgml/release-8.4.sgml | 235 ++++++++++++++++++- doc/src/sgml/release-9.0.sgml | 303 ++++++++++++++++++++++++- doc/src/sgml/release-9.1.sgml | 340 +++++++++++++++++++++++++++- doc/src/sgml/release-9.2.sgml | 415 +++++++++++++++++++++++++++++++++- 4 files changed, 1280 insertions(+), 13 deletions(-) diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml index 03f31e63a84..506743cd2dc 100644 --- a/doc/src/sgml/release-8.4.sgml +++ b/doc/src/sgml/release-8.4.sgml @@ -1,6 +1,235 @@ + + Release 8.4.17 + + + Release Date + 2013-04-04 + + + + This release contains a variety of fixes from 8.4.16. + For information about new features in the 8.4 major release, see + . + + + + Migration to Version 8.4.17 + + + A dump/restore is not required for those running 8.4.X. + + + + However, this release corrects several errors in management of GiST + indexes. After installing this update, it is advisable to + REINDEX any GiST indexes that meet one or more of the + conditions described below. + + + + Also, if you are upgrading from a version earlier than 8.4.10, + see the release notes for 8.4.10. + + + + + + Changes + + + + + + Reset OpenSSL randomness state in each postmaster child process + (Marko Kreen) + + + + This avoids a scenario wherein random numbers generated by + contrib/pgcrypto functions might be relatively easy for + another database user to guess. The risk is only significant when + the postmaster is configured with ssl = on + but most connections don't use SSL encryption. (CVE-2013-1900) + + + + + + Fix GiST indexes to not use fuzzy geometric comparisons when + it's not appropriate to do so (Alexander Korotkov) + + + + The core geometric types perform comparisons using fuzzy + equality, but gist_box_same must do exact comparisons, + else GiST indexes using it might become inconsistent. After installing + this update, users should REINDEX any GiST indexes on + box, polygon, circle, or point + columns, since all of these use gist_box_same. + + + + + + Fix erroneous range-union and penalty logic in GiST indexes that use + contrib/btree_gist for variable-width data types, that is + text, bytea, bit, and numeric + columns (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in useless + index bloat. Users are advised to REINDEX such indexes + after installing this update. + + + + + + Fix bugs in GiST page splitting code for multi-column indexes + (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in indexes + that are unnecessarily inefficient to search. Users are advised to + REINDEX multi-column GiST indexes after installing this + update. + + + + + + Fix infinite-loop risk in regular expression compilation (Tom Lane, + Don Porter) + + + + + + Fix potential null-pointer dereference in regular expression compilation + (Tom Lane) + + + + + + Fix to_char() to use ASCII-only case-folding rules where + appropriate (Tom Lane) + + + + This fixes misbehavior of some template patterns that should be + locale-independent, but mishandled I and + i in Turkish locales. + + + + + + Fix unwanted rejection of timestamp 1999-12-31 24:00:00 + (Tom Lane) + + + + + + Remove useless picksplit doesn't support secondary split log + messages (Josh Hansen, Tom Lane) + + + + This message seems to have been added in expectation of code that was + never written, and probably never will be, since GiST's default + handling of secondary splits is actually pretty good. So stop nagging + end users about it. + + + + + + Fix possible failure to send a session's last few transaction + commit/abort counts to the statistics collector (Tom Lane) + + + + + + Eliminate memory leaks in PL/Perl's spi_prepare() function + (Alex Hunsaker, Tom Lane) + + + + + + Fix pg_dumpall to handle database names containing + = correctly (Heikki Linnakangas) + + + + + + Avoid crash in pg_dump when an incorrect connection + string is given (Heikki Linnakangas) + + + + + + Ignore invalid indexes in pg_dump (Michael Paquier) + + + + Dumping invalid indexes can cause problems at restore time, for example + if the reason the index creation failed was because it tried to enforce + a uniqueness condition not satisfied by the table's data. Also, if the + index creation is in fact still in progress, it seems reasonable to + consider it to be an uncommitted DDL change, which + pg_dump wouldn't be expected to dump anyway. + + + + + + Fix contrib/pg_trgm's similarity() function + to return zero for trigram-less strings (Tom Lane) + + + + Previously it returned NaN due to internal division by zero. + + + + + + Update time zone data files to tzdata release 2013b + for DST law changes in Chile, Haiti, Morocco, Paraguay, and some + Russian areas. Also, historical zone data corrections for numerous + places. + + + + Also, update the time zone abbreviation files for recent changes in + Russia and elsewhere: CHOT, GET, + IRKT, KGT, KRAT, MAGT, + MAWT, MSK, NOVT, OMST, + TKT, VLAT, WST, YAKT, + YEKT now follow their current meanings, and + VOLT (Europe/Volgograd) and MIST + (Antarctica/Macquarie) are added to the default abbreviations list. + + + + + + + + Release 8.4.16 @@ -98,10 +327,10 @@ - The main consequence of this mistake is that lowering vacuum_freeze_min_age - would cause full-table vacuuming scans to occur much more frequently - than intended. + transactions, this mistake prevented autovacuum from using partial-table + scans, so that a full-table scan would always happen instead. diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml index f3340abc7e6..d68d5801d43 100644 --- a/doc/src/sgml/release-9.0.sgml +++ b/doc/src/sgml/release-9.0.sgml @@ -1,6 +1,303 @@ + + Release 9.0.13 + + + Release Date + 2013-04-04 + + + + This release contains a variety of fixes from 9.0.12. + For information about new features in the 9.0 major release, see + . + + + + Migration to Version 9.0.13 + + + A dump/restore is not required for those running 9.0.X. + + + + However, this release corrects several errors in management of GiST + indexes. After installing this update, it is advisable to + REINDEX any GiST indexes that meet one or more of the + conditions described below. + + + + Also, if you are upgrading from a version earlier than 9.0.6, + see the release notes for 9.0.6. + + + + + + Changes + + + + + + Fix insecure parsing of server command-line switches (Mitsumasa + Kondo, Kyotaro Horiguchi) + + + + A connection request containing a database name that begins with + - could be crafted to damage or destroy + files within the server's data directory, even if the request is + eventually rejected. (CVE-2013-1899) + + + + + + Reset OpenSSL randomness state in each postmaster child process + (Marko Kreen) + + + + This avoids a scenario wherein random numbers generated by + contrib/pgcrypto functions might be relatively easy for + another database user to guess. The risk is only significant when + the postmaster is configured with ssl = on + but most connections don't use SSL encryption. (CVE-2013-1900) + + + + + + Fix GiST indexes to not use fuzzy geometric comparisons when + it's not appropriate to do so (Alexander Korotkov) + + + + The core geometric types perform comparisons using fuzzy + equality, but gist_box_same must do exact comparisons, + else GiST indexes using it might become inconsistent. After installing + this update, users should REINDEX any GiST indexes on + box, polygon, circle, or point + columns, since all of these use gist_box_same. + + + + + + Fix erroneous range-union and penalty logic in GiST indexes that use + contrib/btree_gist for variable-width data types, that is + text, bytea, bit, and numeric + columns (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in useless + index bloat. Users are advised to REINDEX such indexes + after installing this update. + + + + + + Fix bugs in GiST page splitting code for multi-column indexes + (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in indexes + that are unnecessarily inefficient to search. Users are advised to + REINDEX multi-column GiST indexes after installing this + update. + + + + + + Fix gist_point_consistent + to handle fuzziness consistently (Alexander Korotkov) + + + + Index scans on GiST indexes on point columns would sometimes + yield results different from a sequential scan, because + gist_point_consistent disagreed with the underlying + operator code about whether to do comparisons exactly or fuzzily. + + + + + + Fix buffer leak in WAL replay (Heikki Linnakangas) + + + + This bug could result in incorrect local pin count errors + during replay, making recovery impossible. + + + + + + Fix race condition in DELETE RETURNING (Tom Lane) + + + + Under the right circumstances, DELETE RETURNING could + attempt to fetch data from a shared buffer that the current process + no longer has any pin on. If some other process changed the buffer + meanwhile, this would lead to garbage RETURNING output, or + even a crash. + + + + + + Fix infinite-loop risk in regular expression compilation (Tom Lane, + Don Porter) + + + + + + Fix potential null-pointer dereference in regular expression compilation + (Tom Lane) + + + + + + Fix to_char() to use ASCII-only case-folding rules where + appropriate (Tom Lane) + + + + This fixes misbehavior of some template patterns that should be + locale-independent, but mishandled I and + i in Turkish locales. + + + + + + Fix unwanted rejection of timestamp 1999-12-31 24:00:00 + (Tom Lane) + + + + + + Fix logic error when a single transaction does UNLISTEN + then LISTEN (Tom Lane) + + + + The session wound up not listening for notify events at all, though it + surely should listen in this case. + + + + + + Remove useless picksplit doesn't support secondary split log + messages (Josh Hansen, Tom Lane) + + + + This message seems to have been added in expectation of code that was + never written, and probably never will be, since GiST's default + handling of secondary splits is actually pretty good. So stop nagging + end users about it. + + + + + + Fix possible failure to send a session's last few transaction + commit/abort counts to the statistics collector (Tom Lane) + + + + + + Eliminate memory leaks in PL/Perl's spi_prepare() function + (Alex Hunsaker, Tom Lane) + + + + + + Fix pg_dumpall to handle database names containing + = correctly (Heikki Linnakangas) + + + + + + Avoid crash in pg_dump when an incorrect connection + string is given (Heikki Linnakangas) + + + + + + Ignore invalid indexes in pg_dump and + pg_upgrade (Michael Paquier, Bruce Momjian) + + + + Dumping invalid indexes can cause problems at restore time, for example + if the reason the index creation failed was because it tried to enforce + a uniqueness condition not satisfied by the table's data. Also, if the + index creation is in fact still in progress, it seems reasonable to + consider it to be an uncommitted DDL change, which + pg_dump wouldn't be expected to dump anyway. + pg_upgrade now also skips invalid indexes rather than + failing. + + + + + + Fix contrib/pg_trgm's similarity() function + to return zero for trigram-less strings (Tom Lane) + + + + Previously it returned NaN due to internal division by zero. + + + + + + Update time zone data files to tzdata release 2013b + for DST law changes in Chile, Haiti, Morocco, Paraguay, and some + Russian areas. Also, historical zone data corrections for numerous + places. + + + + Also, update the time zone abbreviation files for recent changes in + Russia and elsewhere: CHOT, GET, + IRKT, KGT, KRAT, MAGT, + MAWT, MSK, NOVT, OMST, + TKT, VLAT, WST, YAKT, + YEKT now follow their current meanings, and + VOLT (Europe/Volgograd) and MIST + (Antarctica/Macquarie) are added to the default abbreviations list. + + + + + + + + Release 9.0.12 @@ -135,10 +432,10 @@ - The main consequence of this mistake is that lowering vacuum_freeze_min_age - would cause full-table vacuuming scans to occur much more frequently - than intended. + transactions, this mistake prevented autovacuum from using partial-table + scans, so that a full-table scan would always happen instead. diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 172b125e222..0af7f389ecc 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -1,6 +1,340 @@ + + Release 9.1.9 + + + Release Date + 2013-04-04 + + + + This release contains a variety of fixes from 9.1.8. + For information about new features in the 9.1 major release, see + . + + + + Migration to Version 9.1.9 + + + A dump/restore is not required for those running 9.1.X. + + + + However, this release corrects several errors in management of GiST + indexes. After installing this update, it is advisable to + REINDEX any GiST indexes that meet one or more of the + conditions described below. + + + + Also, if you are upgrading from a version earlier than 9.1.6, + see the release notes for 9.1.6. + + + + + + Changes + + + + + + Fix insecure parsing of server command-line switches (Mitsumasa + Kondo, Kyotaro Horiguchi) + + + + A connection request containing a database name that begins with + - could be crafted to damage or destroy + files within the server's data directory, even if the request is + eventually rejected. (CVE-2013-1899) + + + + + + Reset OpenSSL randomness state in each postmaster child process + (Marko Kreen) + + + + This avoids a scenario wherein random numbers generated by + contrib/pgcrypto functions might be relatively easy for + another database user to guess. The risk is only significant when + the postmaster is configured with ssl = on + but most connections don't use SSL encryption. (CVE-2013-1900) + + + + + + Make REPLICATION privilege checks test current user not authenticated + user (Noah Misch) + + + + An unprivileged database user could exploit this mistake to call + pg_start_backup() or pg_stop_backup(), + thus possibly interfering with creation of routine backups. + (CVE-2013-1901) + + + + + + Fix GiST indexes to not use fuzzy geometric comparisons when + it's not appropriate to do so (Alexander Korotkov) + + + + The core geometric types perform comparisons using fuzzy + equality, but gist_box_same must do exact comparisons, + else GiST indexes using it might become inconsistent. After installing + this update, users should REINDEX any GiST indexes on + box, polygon, circle, or point + columns, since all of these use gist_box_same. + + + + + + Fix erroneous range-union and penalty logic in GiST indexes that use + contrib/btree_gist for variable-width data types, that is + text, bytea, bit, and numeric + columns (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in useless + index bloat. Users are advised to REINDEX such indexes + after installing this update. + + + + + + Fix bugs in GiST page splitting code for multi-column indexes + (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in indexes + that are unnecessarily inefficient to search. Users are advised to + REINDEX multi-column GiST indexes after installing this + update. + + + + + + Fix gist_point_consistent + to handle fuzziness consistently (Alexander Korotkov) + + + + Index scans on GiST indexes on point columns would sometimes + yield results different from a sequential scan, because + gist_point_consistent disagreed with the underlying + operator code about whether to do comparisons exactly or fuzzily. + + + + + + Fix buffer leak in WAL replay (Heikki Linnakangas) + + + + This bug could result in incorrect local pin count errors + during replay, making recovery impossible. + + + + + + Fix race condition in DELETE RETURNING (Tom Lane) + + + + Under the right circumstances, DELETE RETURNING could + attempt to fetch data from a shared buffer that the current process + no longer has any pin on. If some other process changed the buffer + meanwhile, this would lead to garbage RETURNING output, or + even a crash. + + + + + + Fix infinite-loop risk in regular expression compilation (Tom Lane, + Don Porter) + + + + + + Fix potential null-pointer dereference in regular expression compilation + (Tom Lane) + + + + + + Fix to_char() to use ASCII-only case-folding rules where + appropriate (Tom Lane) + + + + This fixes misbehavior of some template patterns that should be + locale-independent, but mishandled I and + i in Turkish locales. + + + + + + Fix unwanted rejection of timestamp 1999-12-31 24:00:00 + (Tom Lane) + + + + + + Fix logic error when a single transaction does UNLISTEN + then LISTEN (Tom Lane) + + + + The session wound up not listening for notify events at all, though it + surely should listen in this case. + + + + + + Fix possible planner crash after columns have been added to a view + that's depended on by another view (Tom Lane) + + + + + + Remove useless picksplit doesn't support secondary split log + messages (Josh Hansen, Tom Lane) + + + + This message seems to have been added in expectation of code that was + never written, and probably never will be, since GiST's default + handling of secondary splits is actually pretty good. So stop nagging + end users about it. + + + + + + Fix possible failure to send a session's last few transaction + commit/abort counts to the statistics collector (Tom Lane) + + + + + + Eliminate memory leaks in PL/Perl's spi_prepare() function + (Alex Hunsaker, Tom Lane) + + + + + + Fix pg_dumpall to handle database names containing + = correctly (Heikki Linnakangas) + + + + + + Avoid crash in pg_dump when an incorrect connection + string is given (Heikki Linnakangas) + + + + + + Ignore invalid indexes in pg_dump and + pg_upgrade (Michael Paquier, Bruce Momjian) + + + + Dumping invalid indexes can cause problems at restore time, for example + if the reason the index creation failed was because it tried to enforce + a uniqueness condition not satisfied by the table's data. Also, if the + index creation is in fact still in progress, it seems reasonable to + consider it to be an uncommitted DDL change, which + pg_dump wouldn't be expected to dump anyway. + pg_upgrade now also skips invalid indexes rather than + failing. + + + + + + In pg_basebackup, include only the current server + version's subdirectory when backing up a tablespace (Heikki + Linnakangas) + + + + + + Add a server version check in pg_basebackup and + pg_receivexlog, so they fail cleanly with version + combinations that won't work (Heikki Linnakangas) + + + + + + Fix contrib/pg_trgm's similarity() function + to return zero for trigram-less strings (Tom Lane) + + + + Previously it returned NaN due to internal division by zero. + + + + + + Update time zone data files to tzdata release 2013b + for DST law changes in Chile, Haiti, Morocco, Paraguay, and some + Russian areas. Also, historical zone data corrections for numerous + places. + + + + Also, update the time zone abbreviation files for recent changes in + Russia and elsewhere: CHOT, GET, + IRKT, KGT, KRAT, MAGT, + MAWT, MSK, NOVT, OMST, + TKT, VLAT, WST, YAKT, + YEKT now follow their current meanings, and + VOLT (Europe/Volgograd) and MIST + (Antarctica/Macquarie) are added to the default abbreviations list. + + + + + + + + Release 9.1.8 @@ -149,10 +483,10 @@ - The main consequence of this mistake is that lowering vacuum_freeze_min_age - would cause full-table vacuuming scans to occur much more frequently - than intended. + transactions, this mistake prevented autovacuum from using partial-table + scans, so that a full-table scan would always happen instead. diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml index 61bb925dca4..e7cd66240a6 100644 --- a/doc/src/sgml/release-9.2.sgml +++ b/doc/src/sgml/release-9.2.sgml @@ -1,6 +1,413 @@ + + Release 9.2.4 + + + Release Date + 2013-04-04 + + + + This release contains a variety of fixes from 9.2.3. + For information about new features in the 9.2 major release, see + . + + + + Migration to Version 9.2.4 + + + A dump/restore is not required for those running 9.2.X. + + + + However, this release corrects several errors in management of GiST + indexes. After installing this update, it is advisable to + REINDEX any GiST indexes that meet one or more of the + conditions described below. + + + + Also, if you are upgrading from a version earlier than 9.2.2, + see the release notes for 9.2.2. + + + + + + Changes + + + + + + Fix insecure parsing of server command-line switches (Mitsumasa + Kondo, Kyotaro Horiguchi) + + + + A connection request containing a database name that begins with + - could be crafted to damage or destroy + files within the server's data directory, even if the request is + eventually rejected. (CVE-2013-1899) + + + + + + Reset OpenSSL randomness state in each postmaster child process + (Marko Kreen) + + + + This avoids a scenario wherein random numbers generated by + contrib/pgcrypto functions might be relatively easy for + another database user to guess. The risk is only significant when + the postmaster is configured with ssl = on + but most connections don't use SSL encryption. (CVE-2013-1900) + + + + + + Make REPLICATION privilege checks test current user not authenticated + user (Noah Misch) + + + + An unprivileged database user could exploit this mistake to call + pg_start_backup() or pg_stop_backup(), + thus possibly interfering with creation of routine backups. + (CVE-2013-1901) + + + + + + Fix GiST indexes to not use fuzzy geometric comparisons when + it's not appropriate to do so (Alexander Korotkov) + + + + The core geometric types perform comparisons using fuzzy + equality, but gist_box_same must do exact comparisons, + else GiST indexes using it might become inconsistent. After installing + this update, users should REINDEX any GiST indexes on + box, polygon, circle, or point + columns, since all of these use gist_box_same. + + + + + + Fix erroneous range-union and penalty logic in GiST indexes that use + contrib/btree_gist for variable-width data types, that is + text, bytea, bit, and numeric + columns (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in useless + index bloat. Users are advised to REINDEX such indexes + after installing this update. + + + + + + Fix bugs in GiST page splitting code for multi-column indexes + (Tom Lane) + + + + These errors could result in inconsistent indexes in which some keys + that are present would not be found by searches, and also in indexes + that are unnecessarily inefficient to search. Users are advised to + REINDEX multi-column GiST indexes after installing this + update. + + + + + + Fix gist_point_consistent + to handle fuzziness consistently (Alexander Korotkov) + + + + Index scans on GiST indexes on point columns would sometimes + yield results different from a sequential scan, because + gist_point_consistent disagreed with the underlying + operator code about whether to do comparisons exactly or fuzzily. + + + + + + Fix buffer leak in WAL replay (Heikki Linnakangas) + + + + This bug could result in incorrect local pin count errors + during replay, making recovery impossible. + + + + + + Ensure we do crash recovery before entering archive recovery, if the + database was not stopped cleanly and a recovery.conf file + is present (Heikki Linnakangas, Kyotaro Horiguchi, Mitsumasa Kondo) + + + + This is needed to ensure that the database is consistent in certain + scenarios, such as initializing a standby server with a filesystem + snapshot from a running server. + + + + + + Avoid deleting not-yet-archived WAL files during crash recovery + (Heikki Linnakangas, Fujii Masao) + + + + + + Fix race condition in DELETE RETURNING (Tom Lane) + + + + Under the right circumstances, DELETE RETURNING could + attempt to fetch data from a shared buffer that the current process + no longer has any pin on. If some other process changed the buffer + meanwhile, this would lead to garbage RETURNING output, or + even a crash. + + + + + + Fix infinite-loop risk in regular expression compilation (Tom Lane, + Don Porter) + + + + + + Fix potential null-pointer dereference in regular expression compilation + (Tom Lane) + + + + + + Fix to_char() to use ASCII-only case-folding rules where + appropriate (Tom Lane) + + + + This fixes misbehavior of some template patterns that should be + locale-independent, but mishandled I and + i in Turkish locales. + + + + + + Fix unwanted rejection of timestamp 1999-12-31 24:00:00 + (Tom Lane) + + + + + + Fix SQL-language functions to be safely usable as support + functions for range types (Tom Lane) + + + + + + Fix logic error when a single transaction does UNLISTEN + then LISTEN (Tom Lane) + + + + The session wound up not listening for notify events at all, though it + surely should listen in this case. + + + + + + Fix possible planner crash after columns have been added to a view + that's depended on by another view (Tom Lane) + + + + + + Fix performance issue in EXPLAIN (ANALYZE, TIMING OFF) + (Pavel Stehule) + + + + + + Remove useless picksplit doesn't support secondary split log + messages (Josh Hansen, Tom Lane) + + + + This message seems to have been added in expectation of code that was + never written, and probably never will be, since GiST's default + handling of secondary splits is actually pretty good. So stop nagging + end users about it. + + + + + + Remove vestigial secondary-split support in + gist_box_picksplit() (Tom Lane) + + + + Not only was this implementation of secondary-split not better than the + default implementation, it's actually worse. So remove it and let the + default code path handle the case. + + + + + + Fix possible failure to send a session's last few transaction + commit/abort counts to the statistics collector (Tom Lane) + + + + + + Eliminate memory leaks in PL/Perl's spi_prepare() function + (Alex Hunsaker, Tom Lane) + + + + + + Fix pg_dumpall to handle database names containing + = correctly (Heikki Linnakangas) + + + + + + Avoid crash in pg_dump when an incorrect connection + string is given (Heikki Linnakangas) + + + + + + Ignore invalid indexes in pg_dump and + pg_upgrade (Michael Paquier, Bruce Momjian) + + + + Dumping invalid indexes can cause problems at restore time, for example + if the reason the index creation failed was because it tried to enforce + a uniqueness condition not satisfied by the table's data. Also, if the + index creation is in fact still in progress, it seems reasonable to + consider it to be an uncommitted DDL change, which + pg_dump wouldn't be expected to dump anyway. + pg_upgrade now also skips invalid indexes rather than + failing. + + + + + + In pg_basebackup, include only the current server + version's subdirectory when backing up a tablespace (Heikki + Linnakangas) + + + + + + Add a server version check in pg_basebackup and + pg_receivexlog, so they fail cleanly with version + combinations that won't work (Heikki Linnakangas) + + + + + + Fix contrib/dblink to handle inconsistent settings of + DateStyle or IntervalStyle safely (Daniel + Farina, Tom Lane) + + + + Previously, if the remote server had different settings of these + parameters, ambiguous dates might be read incorrectly. This fix + ensures that datetime and interval columns fetched by a + dblink query will be interpreted correctly. Note however + that inconsistent settings are still risky, since literal values + appearing in SQL commands sent to the remote server might be + interpreted differently than they would be locally. + + + + + + Fix contrib/pg_trgm's similarity() function + to return zero for trigram-less strings (Tom Lane) + + + + Previously it returned NaN due to internal division by zero. + + + + + + Enable building PostgreSQL with Microsoft Visual + Studio 2012 (Brar Piening, Noah Misch) + + + + + + Update time zone data files to tzdata release 2013b + for DST law changes in Chile, Haiti, Morocco, Paraguay, and some + Russian areas. Also, historical zone data corrections for numerous + places. + + + + Also, update the time zone abbreviation files for recent changes in + Russia and elsewhere: CHOT, GET, + IRKT, KGT, KRAT, MAGT, + MAWT, MSK, NOVT, OMST, + TKT, VLAT, WST, YAKT, + YEKT now follow their current meanings, and + VOLT (Europe/Volgograd) and MIST + (Antarctica/Macquarie) are added to the default abbreviations list. + + + + + + + + Release 9.2.3 @@ -235,10 +642,10 @@ - The main consequence of this mistake is that lowering vacuum_freeze_min_age - would cause full-table vacuuming scans to occur much more frequently - than intended. + transactions, this mistake prevented autovacuum from using partial-table + scans, so that a full-table scan would always happen instead. @@ -377,7 +784,7 @@ - Fix pg_upgrade's -O/-o options (Bruce Momjian) + Fix pg_upgrade's -O/-o options (Marti Raudsepp)