[ubuntu/hardy-proposed] postgresql-8.3 8.3.13-0ubuntu8.04 (Accepted)

Martin Pitt martin.pitt at ubuntu.com
Tue Dec 21 20:46:57 GMT 2010


postgresql-8.3 (8.3.13-0ubuntu8.04) hardy-proposed; urgency=low

  * New upstream bug fix release: (LP: #693157)
    - Force the default wal_sync_method to be fdatasync on Linux.
      The default on Linux has actually been fdatasync for many years,
      but recent kernel changes caused PostgreSQL to choose open_datasync
      instead. This choice did not result in any performance improvement,
      and caused outright failures on certain filesystems, notably ext4
      with the data=journal mount option.
    - Fix assorted bugs in WAL replay logic for GIN indexes.
      This could result in "bad buffer id: 0" failures or corruption of
      index contents during replication.
    - Fix recovery from base backup when the starting checkpoint WAL
      record is not in the same WAL segment as its redo point.
    - Fix persistent slowdown of autovacuum workers when multiple workers
      remain active for a long time.
      The effective vacuum_cost_limit for an autovacuum worker could drop
      to nearly zero if it processed enough tables, causing it to run
      extremely slowly.
    - Add support for detecting register-stack overrun on IA64.
      The IA64 architecture has two hardware stacks. Full prevention of
      stack-overrun failures requires checking both.
    - Add a check for stack overflow in copyObject().
      Certain code paths could crash due to stack overflow given a
      sufficiently complex query.
    - Fix detection of page splits in temporary GiST indexes.
      It is possible to have a "concurrent" page split in a temporary
      index, if for example there is an open cursor scanning the index
      when an insertion is done. GiST failed to detect this case and
      hence could deliver wrong results when execution of the cursor
      continued.
    - Avoid memory leakage while "ANALYZE"'ing complex index expressions.
    - Ensure an index that uses a whole-row Var still depends on its
      table.
      An index declared like create index i on t (foo(t.-)) would not
      automatically get dropped when its table was dropped.
    - Do not "inline" a SQL function with multiple OUT parameters.
      This avoids a possible crash due to loss of information about the
      expected result rowtype.
    - Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
      attached to the VALUES part of INSERT ... VALUES.
    - Fix constant-folding of COALESCE() expressions.
      The planner would sometimes attempt to evaluate sub-expressions
      that in fact could never be reached, possibly leading to unexpected
      errors.
    - Fix postmaster crash when connection acceptance (accept() or one of
      the calls made immediately after it) fails, and the postmaster was
      compiled with GSSAPI support.
    - Fix missed unlink of temporary files when log_temp_files is active.
      If an error occurred while attempting to emit the log message, the
      unlink was not done, resulting in accumulation of temp files.
    - Add print functionality for InhRelation nodes.
      This avoids a failure when debug_print_parse is enabled and certain
      types of query are executed.
    - Fix incorrect calculation of distance from a point to a horizontal
      line segment.
      This bug affected several different geometric distance-measurement
      operators.
    - Fix PL/pgSQL's handling of "simple" expressions to not fail in
      recursion or error-recovery cases.
    - Fix PL/Python's handling of set-returning functions.
      Attempts to call SPI functions within the iterator generating a set
      result would fail.
    - Fix bug in "contrib/cube"'s GiST picksplit algorithm.
      This could result in considerable inefficiency, though not actually
      incorrect answers, in a GiST index on a cube column. If you have
      such an index, consider "REINDEX"ing it after installing this
      update.
    - Don't emit "identifier will be truncated" notices in
      "contrib/dblink" except when creating new connections.
    - Fix potential coredump on missing public key in "contrib/pgcrypto".
    - Fix memory leak in "contrib/xml2"'s XPath query functions.

Date: Tue, 21 Dec 2010 21:36:17 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://edge.launchpad.net/ubuntu/hardy/+source/postgresql-8.3/8.3.13-0ubuntu8.04
-------------- next part --------------
Format: 1.8
Date: Tue, 21 Dec 2010 21:36:17 +0100
Source: postgresql-8.3
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-8.3 postgresql-client-8.3 postgresql-server-dev-8.3 postgresql-doc-8.3 postgresql-contrib-8.3 postgresql-plperl-8.3 postgresql-plpython-8.3 postgresql-pltcl-8.3 postgresql postgresql-client postgresql-doc postgresql-contrib
Architecture: source
Version: 8.3.13-0ubuntu8.04
Distribution: hardy-proposed
Urgency: low
Maintainer: Ubuntu Core 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.3
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5     - PostgreSQL C client library
 postgresql - object-relational SQL database (latest version)
 postgresql-8.3 - object-relational SQL database, version 8.3 server
 postgresql-client - front-end programs for PostgreSQL (latest version)
 postgresql-client-8.3 - front-end programs for PostgreSQL 8.3
 postgresql-contrib - additional facilities for PostgreSQL (latest version)
 postgresql-contrib-8.3 - additional facilities for PostgreSQL
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-doc-8.3 - documentation for the PostgreSQL database management system
 postgresql-plperl-8.3 - PL/Perl procedural language for PostgreSQL 8.3
 postgresql-plpython-8.3 - PL/Python procedural language for PostgreSQL 8.3
 postgresql-pltcl-8.3 - PL/Tcl procedural language for PostgreSQL 8.3
 postgresql-server-dev-8.3 - development files for PostgreSQL 8.3 server-side programming
Launchpad-Bugs-Fixed: 693157
Changes: 
 postgresql-8.3 (8.3.13-0ubuntu8.04) hardy-proposed; urgency=low
 .
   * New upstream bug fix release: (LP: #693157)
     - Force the default wal_sync_method to be fdatasync on Linux.
       The default on Linux has actually been fdatasync for many years,
       but recent kernel changes caused PostgreSQL to choose open_datasync
       instead. This choice did not result in any performance improvement,
       and caused outright failures on certain filesystems, notably ext4
       with the data=journal mount option.
     - Fix assorted bugs in WAL replay logic for GIN indexes.
       This could result in "bad buffer id: 0" failures or corruption of
       index contents during replication.
     - Fix recovery from base backup when the starting checkpoint WAL
       record is not in the same WAL segment as its redo point.
     - Fix persistent slowdown of autovacuum workers when multiple workers
       remain active for a long time.
       The effective vacuum_cost_limit for an autovacuum worker could drop
       to nearly zero if it processed enough tables, causing it to run
       extremely slowly.
     - Add support for detecting register-stack overrun on IA64.
       The IA64 architecture has two hardware stacks. Full prevention of
       stack-overrun failures requires checking both.
     - Add a check for stack overflow in copyObject().
       Certain code paths could crash due to stack overflow given a
       sufficiently complex query.
     - Fix detection of page splits in temporary GiST indexes.
       It is possible to have a "concurrent" page split in a temporary
       index, if for example there is an open cursor scanning the index
       when an insertion is done. GiST failed to detect this case and
       hence could deliver wrong results when execution of the cursor
       continued.
     - Avoid memory leakage while "ANALYZE"'ing complex index expressions.
     - Ensure an index that uses a whole-row Var still depends on its
       table.
       An index declared like create index i on t (foo(t.-)) would not
       automatically get dropped when its table was dropped.
     - Do not "inline" a SQL function with multiple OUT parameters.
       This avoids a possible crash due to loss of information about the
       expected result rowtype.
     - Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
       attached to the VALUES part of INSERT ... VALUES.
     - Fix constant-folding of COALESCE() expressions.
       The planner would sometimes attempt to evaluate sub-expressions
       that in fact could never be reached, possibly leading to unexpected
       errors.
     - Fix postmaster crash when connection acceptance (accept() or one of
       the calls made immediately after it) fails, and the postmaster was
       compiled with GSSAPI support.
     - Fix missed unlink of temporary files when log_temp_files is active.
       If an error occurred while attempting to emit the log message, the
       unlink was not done, resulting in accumulation of temp files.
     - Add print functionality for InhRelation nodes.
       This avoids a failure when debug_print_parse is enabled and certain
       types of query are executed.
     - Fix incorrect calculation of distance from a point to a horizontal
       line segment.
       This bug affected several different geometric distance-measurement
       operators.
     - Fix PL/pgSQL's handling of "simple" expressions to not fail in
       recursion or error-recovery cases.
     - Fix PL/Python's handling of set-returning functions.
       Attempts to call SPI functions within the iterator generating a set
       result would fail.
     - Fix bug in "contrib/cube"'s GiST picksplit algorithm.
       This could result in considerable inefficiency, though not actually
       incorrect answers, in a GiST index on a cube column. If you have
       such an index, consider "REINDEX"ing it after installing this
       update.
     - Don't emit "identifier will be truncated" notices in
       "contrib/dblink" except when creating new connections.
     - Fix potential coredump on missing public key in "contrib/pgcrypto".
     - Fix memory leak in "contrib/xml2"'s XPath query functions.
Checksums-Sha1: 
 2d3e40f7a15411703a0c818a14eff463a56039b5 2381 postgresql-8.3_8.3.13-0ubuntu8.04.dsc
 80dd34baa0d3ee4094bfebf31384c4a820fe10fb 14010168 postgresql-8.3_8.3.13.orig.tar.gz
 941514da05cd92a3a4f85aa3154d58227b8a71c7 73787 postgresql-8.3_8.3.13-0ubuntu8.04.diff.gz
Checksums-Sha256: 
 5192e268ce5675f381e5a73f3d33448f7b1b5aa686fb9ca359f12147f07cf2be 2381 postgresql-8.3_8.3.13-0ubuntu8.04.dsc
 e28490b44b22016362b654314180a25bd4bfe719da9293d1ed317fd95e01a14d 14010168 postgresql-8.3_8.3.13.orig.tar.gz
 60afe1f26b9a0f91f6a3e3f6310c4e6367d25cf51135ca5c9323b2b84404bac3 73787 postgresql-8.3_8.3.13-0ubuntu8.04.diff.gz
Files: 
 fbba193e8a58c69b4fd4ce526cb81232 2381 misc optional postgresql-8.3_8.3.13-0ubuntu8.04.dsc
 d845f25acd5ce54acbfcdda8098f2929 14010168 misc optional postgresql-8.3_8.3.13.orig.tar.gz
 30ca68d13fff7fbe5a948b60e8bca803 73787 misc optional postgresql-8.3_8.3.13-0ubuntu8.04.diff.gz
Original-Maintainer: Martin Pitt <mpitt at debian.org>


More information about the Hardy-changes mailing list