[ubuntu/lucid-proposed] postgresql-8.4 8.4.10-0ubuntu0.10.04 (Accepted)

Martin Pitt martin.pitt at ubuntu.com
Thu Dec 15 09:56:35 UTC 2011


postgresql-8.4 (8.4.10-0ubuntu0.10.04) lucid-proposed; urgency=low

  * New upstream release: (LP: #904631)
    - Fix bugs in information_schema.referential_constraints view.
      This view was being insufficiently careful about matching the
      foreign-key constraint to the depended-on primary or unique key
      constraint. That could result in failure to show a foreign key
      constraint at all, or showing it multiple times, or claiming that
      it depends on a different constraint than the one it really does.
      Since the view definition is installed by initdb, merely upgrading
      will not fix the problem. If you need to fix this in an existing
      installation, you can (as a superuser) drop the information_schema
      schema then re-create it by sourcing
      "SHAREDIR/information_schema.sql". (Run pg_config --sharedir if
      you're uncertain where "SHAREDIR" is.) This must be repeated in
      each database to be fixed.
    - Fix incorrect replay of WAL records for GIN index updates.
      This could result in transiently failing to find index entries
      after a crash, or on a hot-standby server. The problem would be
      repaired by the next "VACUUM" of the index, however.
    - Fix TOAST-related data corruption during CREATE TABLE dest AS
      SELECT - FROM src or INSERT INTO dest SELECT * FROM src.
      If a table has been modified by "ALTER TABLE ADD COLUMN", attempts
      to copy its data verbatim to another table could produce corrupt
      results in certain corner cases. The problem can only manifest in
      this precise form in 8.4 and later, but we patched earlier versions
      as well in case there are other code paths that could trigger the
      same bug.
    - Fix race condition during toast table access from stale syscache
      entries.
    - Track dependencies of functions on items used in parameter default
      expressions. Previously, a referenced object could be dropped without
      having dropped or modified the function, leading to misbehavior when the
      function was used. Note that merely installing this update will not fix
      the missing dependency entries; to do that, you'd need to "CREATE OR
      REPLACE" each such function afterwards. If you have functions whose
      defaults depend on non-built-in objects, doing so is recommended.
    - Allow inlining of set-returning SQL functions with multiple OUT
      parameters.
    - Make DatumGetInetP() unpack inet datums that have a 1-byte header,
      and add a new macro, DatumGetInetPP(), that does not.
    - Improve locale support in money type's input and output.
      Aside from not supporting all standard lc_monetary formatting
      options, the input and output functions were inconsistent, meaning
      there were locales in which dumped money values could not be
      re-read.
    - Don't let transform_null_equals affect CASE foo WHEN NULL ...
      constructs. transform_null_equals is only supposed to affect foo = NULL
      expressions written directly by the user, not equality checks
      generated internally by this form of CASE.
    - Change foreign-key trigger creation order to better support
      self-referential foreign keys. For a cascading foreign key that
      references its own table, a row update will fire both the ON UPDATE
      trigger and the CHECK trigger as one event. The ON UPDATE trigger must
      execute first, else the CHECK will check a non-final state of the row
      and possibly throw an inappropriate error. However, the firing order of
      these triggers is determined by their names, which generally sort in
      creation order since the triggers have auto-generated names following
      the convention "RI_ConstraintTrigger_NNNN". A proper fix would require
      modifying that convention, which we will do in 9.2, but it seems risky
      to change it in existing releases. So this patch just changes the
      creation order of the triggers. Users encountering this type of error
      should drop and re-create the foreign key constraint to get its triggers
      into the right order.
    - Avoid floating-point underflow while tracking buffer allocation
      rate.
    - Preserve blank lines within commands in psql's command history.
      The former behavior could cause problems if an empty line was
      removed from within a string literal, for example.
    - Fix pg_dump to dump user-defined casts between auto-generated
      types, such as table rowtypes.
    - Use the preferred version of xsubpp to build PL/Perl, not
      necessarily the operating system's main copy.
    - Fix incorrect coding in "contrib/dict_int" and "contrib/dict_xsyn".
    - Honor query cancel interrupts promptly in pgstatindex().
    - Ensure VPATH builds properly install all server header files.
    - Shorten file names reported in verbose error messages.
      Regular builds have always reported just the name of the C file
      containing the error message call, but VPATH builds formerly
      reported an absolute path name.

Date: Sat, 03 Dec 2011 17:38:40 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Martin Pitt <mpitt at debian.org>
https://launchpad.net/ubuntu/lucid/+source/postgresql-8.4/8.4.10-0ubuntu0.10.04
-------------- next part --------------
Format: 1.8
Date: Sat, 03 Dec 2011 17:38:40 +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.10-0ubuntu0.10.04
Distribution: lucid-proposed
Urgency: low
Maintainer: Martin Pitt <mpitt at debian.org>
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: 904631
Changes: 
 postgresql-8.4 (8.4.10-0ubuntu0.10.04) lucid-proposed; urgency=low
 .
   * New upstream release: (LP: #904631)
     - Fix bugs in information_schema.referential_constraints view.
       This view was being insufficiently careful about matching the
       foreign-key constraint to the depended-on primary or unique key
       constraint. That could result in failure to show a foreign key
       constraint at all, or showing it multiple times, or claiming that
       it depends on a different constraint than the one it really does.
       Since the view definition is installed by initdb, merely upgrading
       will not fix the problem. If you need to fix this in an existing
       installation, you can (as a superuser) drop the information_schema
       schema then re-create it by sourcing
       "SHAREDIR/information_schema.sql". (Run pg_config --sharedir if
       you're uncertain where "SHAREDIR" is.) This must be repeated in
       each database to be fixed.
     - Fix incorrect replay of WAL records for GIN index updates.
       This could result in transiently failing to find index entries
       after a crash, or on a hot-standby server. The problem would be
       repaired by the next "VACUUM" of the index, however.
     - Fix TOAST-related data corruption during CREATE TABLE dest AS
       SELECT - FROM src or INSERT INTO dest SELECT * FROM src.
       If a table has been modified by "ALTER TABLE ADD COLUMN", attempts
       to copy its data verbatim to another table could produce corrupt
       results in certain corner cases. The problem can only manifest in
       this precise form in 8.4 and later, but we patched earlier versions
       as well in case there are other code paths that could trigger the
       same bug.
     - Fix race condition during toast table access from stale syscache
       entries.
     - Track dependencies of functions on items used in parameter default
       expressions. Previously, a referenced object could be dropped without
       having dropped or modified the function, leading to misbehavior when the
       function was used. Note that merely installing this update will not fix
       the missing dependency entries; to do that, you'd need to "CREATE OR
       REPLACE" each such function afterwards. If you have functions whose
       defaults depend on non-built-in objects, doing so is recommended.
     - Allow inlining of set-returning SQL functions with multiple OUT
       parameters.
     - Make DatumGetInetP() unpack inet datums that have a 1-byte header,
       and add a new macro, DatumGetInetPP(), that does not.
     - Improve locale support in money type's input and output.
       Aside from not supporting all standard lc_monetary formatting
       options, the input and output functions were inconsistent, meaning
       there were locales in which dumped money values could not be
       re-read.
     - Don't let transform_null_equals affect CASE foo WHEN NULL ...
       constructs. transform_null_equals is only supposed to affect foo = NULL
       expressions written directly by the user, not equality checks
       generated internally by this form of CASE.
     - Change foreign-key trigger creation order to better support
       self-referential foreign keys. For a cascading foreign key that
       references its own table, a row update will fire both the ON UPDATE
       trigger and the CHECK trigger as one event. The ON UPDATE trigger must
       execute first, else the CHECK will check a non-final state of the row
       and possibly throw an inappropriate error. However, the firing order of
       these triggers is determined by their names, which generally sort in
       creation order since the triggers have auto-generated names following
       the convention "RI_ConstraintTrigger_NNNN". A proper fix would require
       modifying that convention, which we will do in 9.2, but it seems risky
       to change it in existing releases. So this patch just changes the
       creation order of the triggers. Users encountering this type of error
       should drop and re-create the foreign key constraint to get its triggers
       into the right order.
     - Avoid floating-point underflow while tracking buffer allocation
       rate.
     - Preserve blank lines within commands in psql's command history.
       The former behavior could cause problems if an empty line was
       removed from within a string literal, for example.
     - Fix pg_dump to dump user-defined casts between auto-generated
       types, such as table rowtypes.
     - Use the preferred version of xsubpp to build PL/Perl, not
       necessarily the operating system's main copy.
     - Fix incorrect coding in "contrib/dict_int" and "contrib/dict_xsyn".
     - Honor query cancel interrupts promptly in pgstatindex().
     - Ensure VPATH builds properly install all server header files.
     - Shorten file names reported in verbose error messages.
       Regular builds have always reported just the name of the C file
       containing the error message call, but VPATH builds formerly
       reported an absolute path name.
Checksums-Sha1: 
 c647d7142b25d941ce1f47ebc2267b1c2c8429db 3257 postgresql-8.4_8.4.10-0ubuntu0.10.04.dsc
 1ae736d90cc84feb8b604f58fa7aa4e3fa415778 18157949 postgresql-8.4_8.4.10.orig.tar.gz
 9c4350b89e2cc139e830870f0dbf421c3b8041cf 45527 postgresql-8.4_8.4.10-0ubuntu0.10.04.diff.gz
Checksums-Sha256: 
 b5cad1c1d5a69ec627b26784353ccdc8fdda70f5df19cf72063a1b7c0bc01d77 3257 postgresql-8.4_8.4.10-0ubuntu0.10.04.dsc
 8da06d33a08004293d70eac1d006c8af3d8aec6e13b509fdcf0ff800e48c4cd7 18157949 postgresql-8.4_8.4.10.orig.tar.gz
 6fd680d757c1121696c802eb9b1f937a4655314ea3c74425f698c6cf2a36a43b 45527 postgresql-8.4_8.4.10-0ubuntu0.10.04.diff.gz
Files: 
 b2338bb9b4347dfe48c6261720b957ac 3257 database optional postgresql-8.4_8.4.10-0ubuntu0.10.04.dsc
 c2776cf3da7923ac4af0ca5c164016ea 18157949 database optional postgresql-8.4_8.4.10.orig.tar.gz
 2d6ecfe5e4abeae941d2003420f2ef73 45527 database optional postgresql-8.4_8.4.10-0ubuntu0.10.04.diff.gz


More information about the Lucid-changes mailing list