[ubuntu/lucid-proposed] postgresql-8.4 8.4.19-0ubuntu010.04 (Accepted)

[Martin Pitt]

postgresql-8.4 (8.4.19-0ubuntu010.04) lucid-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 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).
    - See HISTORY/changelog.gz for details about bug fixes.

Date: Tue, 03 Dec 2013 11:02:52 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/lucid/+source/postgresql-8.4/8.4.19-0ubuntu010.04
-------------- next part --------------
Format: 1.8
Date: Tue, 03 Dec 2013 11:02:52 +0100
Source: postgresql-8.4
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-8.4 postgresql-client-8.4 postgresql-server-dev-8.4 postgresql-doc-8.4 postgresql-contrib-8.4 postgresql-plperl-8.4 postgresql-plpython-8.4 postgresql-pltcl-8.4 postgresql postgresql-client postgresql-doc postgresql-contrib
Architecture: source
Version: 8.4.19-0ubuntu010.04
Distribution: lucid-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 8.4
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5     - PostgreSQL C client library
 postgresql - object-relational SQL database (supported version)
 postgresql-8.4 - object-relational SQL database, version 8.4 server
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-8.4 - front-end programs for PostgreSQL 8.4
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-contrib-8.4 - additional facilities for PostgreSQL
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-doc-8.4 - documentation for the PostgreSQL database management system
 postgresql-plperl-8.4 - PL/Perl procedural language for PostgreSQL 8.4
 postgresql-plpython-8.4 - PL/Python procedural language for PostgreSQL 8.4
 postgresql-pltcl-8.4 - PL/Tcl procedural language for PostgreSQL 8.4
 postgresql-server-dev-8.4 - development files for PostgreSQL 8.4 server-side programming
Launchpad-Bugs-Fixed: 1257211
Changes: 
 postgresql-8.4 (8.4.19-0ubuntu010.04) lucid-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 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).
     - See HISTORY/changelog.gz for details about bug fixes.
Checksums-Sha1: 
 b63cad280c04a1af7bbcc7a83ab5f216c95b4295 3332 postgresql-8.4_8.4.19-0ubuntu010.04.dsc
 1a48ce09f236e889b3794b347afa5a04ef5b8679 18624056 postgresql-8.4_8.4.19.orig.tar.gz
 40fddc570cef948c76365c4e9c5180fa24a99146 53570 postgresql-8.4_8.4.19-0ubuntu010.04.diff.gz
Checksums-Sha256: 
 67c326ee3cebe33dcbd4158c546b6145a6ae08aada3b79fd83c8a929b791f09f 3332 postgresql-8.4_8.4.19-0ubuntu010.04.dsc
 39aebaac437ecfbcc37d67d8ab73f56e395e12a1be378b25b857e33dbf7ce657 18624056 postgresql-8.4_8.4.19.orig.tar.gz
 1a3fa865d59d7ecaa2f03d5e660c62781cd9a0d2e7c362c4ea35340e1ac6e7f9 53570 postgresql-8.4_8.4.19-0ubuntu010.04.diff.gz
Files: 
 f410109dd2b10dd0b1d35511a17c6c13 3332 database optional postgresql-8.4_8.4.19-0ubuntu010.04.dsc
 7fc3587b209a0b032462b1ae440f03aa 18624056 database optional postgresql-8.4_8.4.19.orig.tar.gz
 52c9f00659b6b6d405005970064cb922 53570 database optional postgresql-8.4_8.4.19-0ubuntu010.04.diff.gz
Original-Maintainer: Martin Pitt <mpitt at debian.org>