+
+
Release 8.4.21
+
+
+
Release Date
+ 2014-03-20
+
+
+ This release contains a variety of fixes from 8.4.20.
+ For information about new features in the 8.4 major release, see
+ .
+
+
+ The
PostgreSQL community will stop releasing updates+ for the 8.4.X release series in July 2014.
+ Users are encouraged to update to a newer release branch soon.
+
+
+
+
Migration to Version 8.4.21
+
+ A dump/restore is not required for those running 8.4.X.
+
+
+ However, if you are upgrading from a version earlier than 8.4.19,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Restore GIN metapages unconditionally to avoid torn-page risk
+ (Heikki Linnakangas)
+
+
+ Although this oversight could theoretically result in a corrupted
+ index, it is unlikely to have caused any problems in practice, since
+ the active part of a GIN metapage is smaller than a standard 512-byte
+ disk sector.
+
+
+
+
+ Allow regular-expression operators to be terminated early by query
+ cancel requests (Tom Lane)
+
+
+ This prevents scenarios wherein a pathological regular expression
+ could lock up a server process uninterruptably for a long time.
+
+
+
+
+ Remove incorrect code that tried to allow OVERLAPS with
+ single-element row arguments (Joshua Yanovski)
+
+
+ This code never worked correctly, and since the case is neither
+ specified by the SQL standard nor documented, it seemed better to
+ remove it than fix it.
+
+
+
+
+ Avoid getting more than AccessShareLock when de-parsing a
+ rule or view (Dean Rasheed)
+
+
+ This oversight resulted in
pg_dump unexpectedly+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
+ commands in rules. While usually harmless, that could interfere with
+ concurrent transactions that tried to acquire, for example,
+ ShareLock on those tables.
+
+
+
+
+ Prevent interrupts while reporting non-ERROR messages
+ (Tom Lane)
+
+
+ This guards against rare server-process freezeups due to recursive
+ entry to syslog(), and perhaps other related problems.
+
+
+
+
+ Update time zone data files to
tzdata release 2014a+ for DST law changes in Fiji and Turkey, plus historical changes in
+ Israel and Ukraine.
+
+
+
+
+
+
+
+
+
+
Release 8.4.20
+
+
Release 9.0.17
+
+
+
Release Date
+ 2014-03-20
+
+
+ This release contains a variety of fixes from 9.0.16.
+ For information about new features in the 9.0 major release, see
+ .
+
+
+
+
Migration to Version 9.0.17
+
+ A dump/restore is not required for those running 9.0.X.
+
+
+ However, if you are upgrading from a version earlier than 9.0.15,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Restore GIN metapages unconditionally to avoid torn-page risk
+ (Heikki Linnakangas)
+
+
+ Although this oversight could theoretically result in a corrupted
+ index, it is unlikely to have caused any problems in practice, since
+ the active part of a GIN metapage is smaller than a standard 512-byte
+ disk sector.
+
+
+
+
+ Avoid race condition in checking transaction commit status during
+ receipt of a NOTIFY message (Marko Tiikkaja)
+
+
+ This prevents a scenario wherein a sufficiently fast client might
+ respond to a notification before database updates made by the
+ notifier have become visible to the recipient.
+
+
+
+
+ Allow regular-expression operators to be terminated early by query
+ cancel requests (Tom Lane)
+
+
+ This prevents scenarios wherein a pathological regular expression
+ could lock up a server process uninterruptably for a long time.
+
+
+
+
+ Remove incorrect code that tried to allow OVERLAPS with
+ single-element row arguments (Joshua Yanovski)
+
+
+ This code never worked correctly, and since the case is neither
+ specified by the SQL standard nor documented, it seemed better to
+ remove it than fix it.
+
+
+
+
+ Avoid getting more than AccessShareLock when de-parsing a
+ rule or view (Dean Rasheed)
+
+
+ This oversight resulted in
pg_dump unexpectedly+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
+ commands in rules. While usually harmless, that could interfere with
+ concurrent transactions that tried to acquire, for example,
+ ShareLock on those tables.
+
+
+
+
+ Improve performance of index endpoint probes during planning (Tom Lane)
+
+
+ This change fixes a significant performance problem that occurred
+ when there were many not-yet-committed rows at the end of the index,
+ which is a common situation for indexes on sequentially-assigned
+ values such as timestamps or sequence-generated identifiers.
+
+
+
+
+ Fix test to see if hot standby connections can be allowed immediately
+ after a crash (Heikki Linnakangas)
+
+
+
+
+ Prevent interrupts while reporting non-ERROR messages
+ (Tom Lane)
+
+
+ This guards against rare server-process freezeups due to recursive
+ entry to syslog(), and perhaps other related problems.
+
+
+
+
+ Prevent intermittent could not reserve shared memory region
+ failures on recent Windows versions (MauMau)
+
+
+
+
+ Update time zone data files to
tzdata release 2014a+ for DST law changes in Fiji and Turkey, plus historical changes in
+ Israel and Ukraine.
+
+
+
+
+
+
+
+
+
+
Release 9.0.16
+
+
Release 9.1.13
+
+
+
Release Date
+ 2014-03-20
+
+
+ This release contains a variety of fixes from 9.1.12.
+ For information about new features in the 9.1 major release, see
+ .
+
+
+
+
Migration to Version 9.1.13
+
+ A dump/restore is not required for those running 9.1.X.
+
+
+ However, if you are upgrading from a version earlier than 9.1.11,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Restore GIN metapages unconditionally to avoid torn-page risk
+ (Heikki Linnakangas)
+
+
+ Although this oversight could theoretically result in a corrupted
+ index, it is unlikely to have caused any problems in practice, since
+ the active part of a GIN metapage is smaller than a standard 512-byte
+ disk sector.
+
+
+
+
+ Avoid race condition in checking transaction commit status during
+ receipt of a NOTIFY message (Marko Tiikkaja)
+
+
+ This prevents a scenario wherein a sufficiently fast client might
+ respond to a notification before database updates made by the
+ notifier have become visible to the recipient.
+
+
+
+
+ Allow regular-expression operators to be terminated early by query
+ cancel requests (Tom Lane)
+
+
+ This prevents scenarios wherein a pathological regular expression
+ could lock up a server process uninterruptably for a long time.
+
+
+
+
+ Remove incorrect code that tried to allow OVERLAPS with
+ single-element row arguments (Joshua Yanovski)
+
+
+ This code never worked correctly, and since the case is neither
+ specified by the SQL standard nor documented, it seemed better to
+ remove it than fix it.
+
+
+
+
+ Avoid getting more than AccessShareLock when de-parsing a
+ rule or view (Dean Rasheed)
+
+
+ This oversight resulted in
pg_dump unexpectedly+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
+ commands in rules. While usually harmless, that could interfere with
+ concurrent transactions that tried to acquire, for example,
+ ShareLock on those tables.
+
+
+
+
+ Improve performance of index endpoint probes during planning (Tom Lane)
+
+
+ This change fixes a significant performance problem that occurred
+ when there were many not-yet-committed rows at the end of the index,
+ which is a common situation for indexes on sequentially-assigned
+ values such as timestamps or sequence-generated identifiers.
+
+
+
+
+ Fix
walsender's failure to shut down cleanly when client+ is
pg_receivexlog (Fujii Masao)+
+
+
+
+ Fix test to see if hot standby connections can be allowed immediately
+ after a crash (Heikki Linnakangas)
+
+
+
+
+ Prevent interrupts while reporting non-ERROR messages
+ (Tom Lane)
+
+
+ This guards against rare server-process freezeups due to recursive
+ entry to syslog(), and perhaps other related problems.
+
+
+
+
+ Fix memory leak in PL/Perl when returning a composite result, including
+ multiple-OUT-parameter cases (Alex Hunsaker)
+
+
+
+
+ Prevent intermittent could not reserve shared memory region
+ failures on recent Windows versions (MauMau)
+
+
+
+
+ Update time zone data files to
tzdata release 2014a+ for DST law changes in Fiji and Turkey, plus historical changes in
+ Israel and Ukraine.
+
+
+
+
+
+
+
+
+
+
Release 9.1.12
+
+
Release 9.2.8
+
+
+
Release Date
+ 2014-03-20
+
+
+ This release contains a variety of fixes from 9.2.7.
+ For information about new features in the 9.2 major release, see
+ .
+
+
+
+
Migration to Version 9.2.8
+
+ A dump/restore is not required for those running 9.2.X.
+
+
+ However, if you are upgrading from a version earlier than 9.2.6,
+ see .
+
+
+
+
+
+
Changes
+
+
+
+
+ Restore GIN metapages unconditionally to avoid torn-page risk
+ (Heikki Linnakangas)
+
+
+ Although this oversight could theoretically result in a corrupted
+ index, it is unlikely to have caused any problems in practice, since
+ the active part of a GIN metapage is smaller than a standard 512-byte
+ disk sector.
+
+
+
+
+ Avoid race condition in checking transaction commit status during
+ receipt of a NOTIFY message (Marko Tiikkaja)
+
+
+ This prevents a scenario wherein a sufficiently fast client might
+ respond to a notification before database updates made by the
+ notifier have become visible to the recipient.
+
+
+
+
+ Allow regular-expression operators to be terminated early by query
+ cancel requests (Tom Lane)
+
+
+ This prevents scenarios wherein a pathological regular expression
+ could lock up a server process uninterruptably for a long time.
+
+
+
+
+ Remove incorrect code that tried to allow OVERLAPS with
+ single-element row arguments (Joshua Yanovski)
+
+
+ This code never worked correctly, and since the case is neither
+ specified by the SQL standard nor documented, it seemed better to
+ remove it than fix it.
+
+
+
+
+ Avoid getting more than AccessShareLock when de-parsing a
+ rule or view (Dean Rasheed)
+
+
+ This oversight resulted in
pg_dump unexpectedly+ acquiring RowExclusiveLock locks on tables mentioned as
+ the targets of INSERT/UPDATE/DELETE
+ commands in rules. While usually harmless, that could interfere with
+ concurrent transactions that tried to acquire, for example,
+ ShareLock on those tables.
+
+
+
+
+ Improve performance of index endpoint probes during planning (Tom Lane)
+
+
+ This change fixes a significant performance problem that occurred
+ when there were many not-yet-committed rows at the end of the index,
+ which is a common situation for indexes on sequentially-assigned
+ values such as timestamps or sequence-generated identifiers.
+
+
+
+
+ Fix
walsender's failure to shut down cleanly when client+ is
pg_receivexlog (Fujii Masao)+
+
+
+
+ Check WAL level and hot standby parameters correctly when doing crash
+ recovery that will be followed by archive recovery (Heikki Linnakangas)
+
+
+
+
+ Fix test to see if hot standby connections can be allowed immediately
+ after a crash (Heikki Linnakangas)
+
+
+
+
+ Prevent interrupts while reporting non-ERROR messages
+ (Tom Lane)
+
+
+ This guards against rare server-process freezeups due to recursive
+ entry to syslog(), and perhaps other related problems.
+
+
+
+
+ Fix memory leak in PL/Perl when returning a composite result, including
+ multiple-OUT-parameter cases (Alex Hunsaker)
+
+
+
+
+ Fix tracking of
psql script line numbers+ during \copy from out-of-line data
+ (Kumar Rajeev Rastogi, Amit Khandekar)
+
+
+ \copy ... from incremented the script file line number
+ for each data line, even if the data was not coming from the script
+ file. This mistake resulted in wrong line numbers being reported for
+ any errors occurring later in the same script file.
+
+
+
+
+ Prevent intermittent could not reserve shared memory region
+ failures on recent Windows versions (MauMau)
+
+
+
+
+ Update time zone data files to
tzdata release 2014a+ for DST law changes in Fiji and Turkey, plus historical changes in
+ Israel and Ukraine.
+
+
+
+
+
+
+
+
+
+
Release 9.2.7
this update.
- Also, the error fixed in the second changelog entry below could have
- caused some bloat in statistics data. Users who have done
- many DROP DATABASE commands since upgrading to 9.3 may wish
- to manually remove files in $PGDATA/pg_stat_tmp
- (or $PGDATA/pg_stat if the server is not running) that
- have old modification times and do not correspond to any database OID
- present in $PGDATA/base. If you do this, note that the
- file db_0.stat is a valid file even though it does not
- correspond to any $PGDATA/base subdirectory.
-
-
Also, if you are upgrading from a version earlier than 9.3.3,
see .
- This error allowed multiple versions of the same row to become
- visible to queries, resulting in apparent duplicates. Since the
- error is in WAL replay, it would only manifest during crash recovery
- or on standby servers.
-
-
-
-
-
-
- Remove the correct per-database statistics file during DROP
- DATABASE (Tomas Vondra)
-
-
- This fix prevents a permanent leak of statistics file space.
+ This error caused updated rows to not be found by index scans, resulting
+ in inconsistent query results depending on whether an index scan was
+ used. Subsequent processing could result in constraint violations,
+ since the previously updated row would not be found by later index
+ searches, thus possibly allowing conflicting rows to be inserted.
+ Since this error is in WAL replay, it would only manifest during crash
+ recovery or on standby servers. The improperly-replayed case most
+ commonly arises when a table row that is referenced by a foreign-key
+ constraint is updated concurrently with creation of a referencing row.
+
+
+
+ Remove the correct per-database statistics file during DROP
+ DATABASE (Tomas Vondra)
+
+
+ This fix prevents a permanent leak of statistics file space.
+ Users who have done many DROP DATABASE commands since
+ upgrading to
PostgreSQL 9.3 may wish to check their+ statistics directory and delete statistics files that do not
+ correspond to any existing database. Please note
+ that db_0.stat should not be removed.
+
+
+
+
+
+ Fix
walsender's failure to shut down cleanly when client+ is
pg_receivexlog (Fujii Masao)+
+
+
+
+
+ Fix memory leak in PL/Perl when returning a composite result, including
+ multiple-OUT-parameter cases (Alex Hunsaker)
+
+
+
projects / postgresql.git / commitdiff