[ubuntu/oneiric] postgresql-8.4 8.4.8-1 (Accepted)

[Ubuntu Installer]

postgresql-8.4 (8.4.8-1) unstable; urgency=medium

  Priority medium due to data-loss pg_upgrade bug.

  [ Martin Pitt ]
  * New upstream bug fix release:
    - If your installation was upgraded from a previous major release by
      running pg_upgrade, you should take action to prevent possible data loss
      due to a now-fixed bug in pg_upgrade. The recommended solution is to run
      "VACUUM FREEZE" on all TOAST tables.  More information is available at
      http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.
    - Fix pg_upgrade's handling of TOAST tables.
      This error poses a significant risk of data loss for installations
      that have been upgraded with pg_upgrade. This patch corrects the
      problem for future uses of pg_upgrade, but does not in itself cure
      the issue in installations that have been processed with a buggy
      version of pg_upgrade.
    - Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set"
      warning.
    - Disallow including a composite type in itself.
    - Avoid potential deadlock during catalog cache initialization.
    - Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling
      when there was a concurrent update to the target tuple.
    - Disallow "DROP TABLE" when there are pending deferred trigger
      events for the table.
      Formerly the "DROP" would go through, leading to "could not open
      relation with OID nnn" errors when the triggers were eventually
      fired.
    - Prevent crash triggered by constant-false WHERE conditions during
      GEQO optimization.
    - Improve planner's handling of semi-join and anti-join cases.
    - Fix selectivity estimation for text search to account for NULLs.
    - Improve PL/pgSQL's ability to handle row types with dropped columns.
    - Fix PL/Python memory leak involving array slices.
    - Fix pg_restore to cope with long lines (over 1KB) in TOC files.
    - Put in more safeguards against crashing due to division-by-zero
      with overly enthusiastic compiler optimization. (Closes: #616180)
  * debian/control: Stop building the versionless metapackages and client-side
    libraries, they are built by postgresql-9.0 now. Add libpq-dev build
    dependency.
  * debian/rules: Drop check for uninstalled files, since it'd now break the
    build due to the uninstalled libraries.
  
  [ Matthias Klose ]
  * Add 15-bool-altivec.patch: Fix definition of bool on __APPLE_ALTIVEC__
    architecture (ppc64).

Date: Tue,  03 May 2011 07:46:46 +0000
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Martin Pitt <mpitt at debian.org>
Origin: Debian/unstable
https://launchpad.net/ubuntu/oneiric/+source/postgresql-8.4/8.4.8-1
-------------- next part --------------
Origin: Debian/unstable
Format: 1.7
Date: Tue,  03 May 2011 07:46:46 +0000
Source: postgresql-8.4
Binary: 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
Architecture: source
Version: 8.4.8-1
Distribution: oneiric
Urgency: medium
Maintainer: Martin Pitt <mpitt at debian.org>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description:
 postgresql-8.4 - object-relational SQL database, version 8.4 server
Closes: 616180
Files:
 15b35cad88f630d579a23d3c50768a36 41088 database optional postgresql-8.4_8.4.8-1.diff.gz
 9dece918943725fd4fab02f14e32d39b 2349 database optional postgresql-8.4_8.4.8-1.dsc
Changes:
 postgresql-8.4 (8.4.8-1) unstable; urgency=medium
 .
   Priority medium due to data-loss pg_upgrade bug.
 .
   [ Martin Pitt ]
   * New upstream bug fix release:
     - If your installation was upgraded from a previous major release by
       running pg_upgrade, you should take action to prevent possible data loss
       due to a now-fixed bug in pg_upgrade. The recommended solution is to run
       "VACUUM FREEZE" on all TOAST tables.  More information is available at
       http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.
     - Fix pg_upgrade's handling of TOAST tables.
       This error poses a significant risk of data loss for installations
       that have been upgraded with pg_upgrade. This patch corrects the
       problem for future uses of pg_upgrade, but does not in itself cure
       the issue in installations that have been processed with a buggy
       version of pg_upgrade.
     - Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set"
       warning.
     - Disallow including a composite type in itself.
     - Avoid potential deadlock during catalog cache initialization.
     - Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling
       when there was a concurrent update to the target tuple.
     - Disallow "DROP TABLE" when there are pending deferred trigger
       events for the table.
       Formerly the "DROP" would go through, leading to "could not open
       relation with OID nnn" errors when the triggers were eventually
       fired.
     - Prevent crash triggered by constant-false WHERE conditions during
       GEQO optimization.
     - Improve planner's handling of semi-join and anti-join cases.
     - Fix selectivity estimation for text search to account for NULLs.
     - Improve PL/pgSQL's ability to handle row types with dropped columns.
     - Fix PL/Python memory leak involving array slices.
     - Fix pg_restore to cope with long lines (over 1KB) in TOC files.
     - Put in more safeguards against crashing due to division-by-zero
       with overly enthusiastic compiler optimization. (Closes: #616180)
   * debian/control: Stop building the versionless metapackages and client-side
     libraries, they are built by postgresql-9.0 now. Add libpq-dev build
     dependency.
   * debian/rules: Drop check for uninstalled files, since it'd now break the
     build due to the uninstalled libraries.
   
   [ Matthias Klose ]
   * Add 15-bool-altivec.patch: Fix definition of bool on __APPLE_ALTIVEC__
     architecture (ppc64).