[ubuntu/raring-proposed] postgresql-9.1 9.1.11-0ubuntu0.13.04 (Accepted)

Martin Pitt martin.pitt at ubuntu.com
Fri Dec 6 05:59:43 UTC 2013 

postgresql-9.1 (9.1.11-0ubuntu0.13.04) raring-proposed; urgency=low

  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      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.
      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.
    - See HISTORY/changelog.gz for details about other bug fixes.

Date: Tue, 03 Dec 2013 10:22:12 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/raring/+source/postgresql-9.1/9.1.11-0ubuntu0.13.04
-------------- next part --------------
Format: 1.8
Date: Tue, 03 Dec 2013 10:22:12 +0100
Source: postgresql-9.1
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-9.1 postgresql-9.1-dbg postgresql-client-9.1 postgresql-server-dev-9.1 postgresql-doc-9.1 postgresql-contrib-9.1 postgresql-plperl-9.1 postgresql-plpython-9.1 postgresql-plpython3-9.1 postgresql-pltcl-9.1
Architecture: source
Version: 9.1.11-0ubuntu0.13.04
Distribution: raring-proposed
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description: 
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 9.1
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5     - PostgreSQL C client library
 postgresql-9.1 - object-relational SQL database, version 9.1 server
 postgresql-9.1-dbg - debug symbols for postgresql-9.1
 postgresql-client-9.1 - front-end programs for PostgreSQL 9.1
 postgresql-contrib-9.1 - additional facilities for PostgreSQL
 postgresql-doc-9.1 - documentation for the PostgreSQL database management system
 postgresql-plperl-9.1 - PL/Perl procedural language for PostgreSQL 9.1
 postgresql-plpython-9.1 - PL/Python procedural language for PostgreSQL 9.1
 postgresql-plpython3-9.1 - PL/Python 3 procedural language for PostgreSQL 9.1
 postgresql-pltcl-9.1 - PL/Tcl procedural language for PostgreSQL 9.1
 postgresql-server-dev-9.1 - development files for PostgreSQL 9.1 server-side programming
Launchpad-Bugs-Fixed: 1257211
Changes: 
 postgresql-9.1 (9.1.11-0ubuntu0.13.04) raring-proposed; urgency=low
 .
   * New upstream bug fix release. (LP: #1257211)
     - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
       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.
       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.
     - See HISTORY/changelog.gz for details about other bug fixes.
Checksums-Sha1: 
 7d66fe4c011e5773cd2354ca01d5c60539c3ed64 3457 postgresql-9.1_9.1.11-0ubuntu0.13.04.dsc
 b9ee975498705647aae77dae91869bfc6bb079ff 15861805 postgresql-9.1_9.1.11.orig.tar.bz2
 edaa0946cd4e1274c5625692824f0878f10c11e7 37678 postgresql-9.1_9.1.11-0ubuntu0.13.04.debian.tar.gz
Checksums-Sha256: 
 dacc5aac733b852d811a4a87a82a80fe230875db9acce9be5925f70b30ed514b 3457 postgresql-9.1_9.1.11-0ubuntu0.13.04.dsc
 ccbc35aae1490ee5878b97a6aea48dad7465cdad296b380542e4303b68cc6f74 15861805 postgresql-9.1_9.1.11.orig.tar.bz2
 5f892f0de72efad23f0fd3a430b04041411d9ab3d872ed98800de1fcc4cb010c 37678 postgresql-9.1_9.1.11-0ubuntu0.13.04.debian.tar.gz
Files: 
 4f0e6b1ae5a71c46d2585942b568333d 3457 database optional postgresql-9.1_9.1.11-0ubuntu0.13.04.dsc
 863caa3d9f57ab3cd031fd06f497e1b6 15861805 database optional postgresql-9.1_9.1.11.orig.tar.bz2
 506b5de8a2b4bb3f249ef5ef66abd203 37678 database optional postgresql-9.1_9.1.11-0ubuntu0.13.04.debian.tar.gz
Original-Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public at lists.alioth.debian.org>

More information about the Raring-changes mailing list