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

Martin Pitt martin.pitt at ubuntu.com
Wed Mar 25 12:32:43 GMT 2009


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

  * New upstream bug fix release: (LP: #344688)
    - Prevent error recursion crashes when encoding conversion fails.
      This change extends fixes made in the last two minor releases for
      related failure scenarios. The previous fixes were narrowly
      tailored for the original problem reports, but we have now
      recognized that *any* error thrown by an encoding conversion
      function could potentially lead to infinite recursion while trying
      to report the error. The solution therefore is to disable
      translation and encoding conversion and report the plain-ASCII form
      of any error message, if we find we have gotten into a recursive
      error reporting situation. (Closes: #517405)
    - Disallow "CREATE CONVERSION" with the wrong encodings for the
      specified conversion function. This prevents one possible scenario for
      encoding conversion failure. The previous change is a backstop to guard
      against other kinds of failures in the same area.
    - Fix xpath() to not modify the path expression unless necessary, and
      to make a saner attempt at it when necessary.
      The SQL standard suggests that xpath should work on data that is a
      document fragment, but libxml doesn't support that, and indeed it's
      not clear that this is sensible according to the XPath standard.
      xpath attempted to work around this mismatch by modifying both the
      data and the path expression, but the modification was buggy and
      could cause valid searches to fail. Now, xpath checks whether the
      data is in fact a well-formed document, and if so invokes libxml
      with no change to the data or path expression. Otherwise, a
      different modification method that is somewhat less likely to fail
      is used.
      Note: The new modification method is still not 100% satisfactory,
      and it seems likely that no real solution is possible. This patch
      should therefore be viewed as a band-aid to keep from breaking
      existing applications unnecessarily. It is likely that PostgreSQL
      8.4 will simply reject use of xpath on data that is not a
      well-formed document.
    - Fix core dump when to_char() is given format codes that are
      inappropriate for the type of the data argument.
    - Fix extreme inefficiency in text search parser's handling of an
      email-like string containing multiple @ characters.
    - Fix planner problem with sub-"SELECT" in the output list of a
      larger subquery.
    - Fix decompilation of CASE WHEN with an implicit coercion.
    - Fix possible misassignment of the owner of a TOAST table's rowtype.
      If "CLUSTER" or a rewriting variant of "ALTER TABLE" were executed
      by someone other than the table owner, the pg_type entry for the
      table's TOAST table would end up marked as owned by that someone.
      This caused no immediate problems, since the permissions on the
      TOAST rowtype aren't examined by any ordinary database operation.
      However, it could lead to unexpected failures if one later tried to
      drop the role that issued the command (in 8.1 or 8.2), or "owner of
      data type appears to be invalid" warnings from pg_dump after having
      done so (in 8.3).
    - Change "UNLISTEN" to exit quickly if the current session has never
      executed any "LISTEN" command.
      Most of the time this is not a particularly useful optimization,
      but since "DISCARD ALL" invokes "UNLISTEN", the previous coding
      caused a substantial performance problem for applications that made
      heavy use of "DISCARD ALL".
    - Fix PL/pgSQL to not treat INTO after "INSERT" as an INTO-variables
      clause anywhere in the string, not only at the start; in
      particular, don't fail for "INSERT INTO" within "CREATE RULE".
    - Clean up PL/pgSQL error status variables fully at block exit.
      This is not a problem for PL/pgSQL itself, but the omission could
      cause the PL/pgSQL Debugger to crash while examining the state of a
      function.
    - Add MUST (Mauritius Island Summer Time) to the default list of
      known timezone abbreviations.

Date: Wed, 25 Mar 2009 09:13:38 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/hardy/+source/postgresql-8.3/8.3.7-0ubuntu8.04
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 25 Mar 2009 09:13:38 +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.7-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
Closes: 517405
Launchpad-Bugs-Fixed: 344688
Changes: 
 postgresql-8.3 (8.3.7-0ubuntu8.04) hardy-proposed; urgency=low
 .
   * New upstream bug fix release: (LP: #344688)
     - Prevent error recursion crashes when encoding conversion fails.
       This change extends fixes made in the last two minor releases for
       related failure scenarios. The previous fixes were narrowly
       tailored for the original problem reports, but we have now
       recognized that *any* error thrown by an encoding conversion
       function could potentially lead to infinite recursion while trying
       to report the error. The solution therefore is to disable
       translation and encoding conversion and report the plain-ASCII form
       of any error message, if we find we have gotten into a recursive
       error reporting situation. (Closes: #517405)
     - Disallow "CREATE CONVERSION" with the wrong encodings for the
       specified conversion function. This prevents one possible scenario for
       encoding conversion failure. The previous change is a backstop to guard
       against other kinds of failures in the same area.
     - Fix xpath() to not modify the path expression unless necessary, and
       to make a saner attempt at it when necessary.
       The SQL standard suggests that xpath should work on data that is a
       document fragment, but libxml doesn't support that, and indeed it's
       not clear that this is sensible according to the XPath standard.
       xpath attempted to work around this mismatch by modifying both the
       data and the path expression, but the modification was buggy and
       could cause valid searches to fail. Now, xpath checks whether the
       data is in fact a well-formed document, and if so invokes libxml
       with no change to the data or path expression. Otherwise, a
       different modification method that is somewhat less likely to fail
       is used.
       Note: The new modification method is still not 100% satisfactory,
       and it seems likely that no real solution is possible. This patch
       should therefore be viewed as a band-aid to keep from breaking
       existing applications unnecessarily. It is likely that PostgreSQL
       8.4 will simply reject use of xpath on data that is not a
       well-formed document.
     - Fix core dump when to_char() is given format codes that are
       inappropriate for the type of the data argument.
     - Fix extreme inefficiency in text search parser's handling of an
       email-like string containing multiple @ characters.
     - Fix planner problem with sub-"SELECT" in the output list of a
       larger subquery.
     - Fix decompilation of CASE WHEN with an implicit coercion.
     - Fix possible misassignment of the owner of a TOAST table's rowtype.
       If "CLUSTER" or a rewriting variant of "ALTER TABLE" were executed
       by someone other than the table owner, the pg_type entry for the
       table's TOAST table would end up marked as owned by that someone.
       This caused no immediate problems, since the permissions on the
       TOAST rowtype aren't examined by any ordinary database operation.
       However, it could lead to unexpected failures if one later tried to
       drop the role that issued the command (in 8.1 or 8.2), or "owner of
       data type appears to be invalid" warnings from pg_dump after having
       done so (in 8.3).
     - Change "UNLISTEN" to exit quickly if the current session has never
       executed any "LISTEN" command.
       Most of the time this is not a particularly useful optimization,
       but since "DISCARD ALL" invokes "UNLISTEN", the previous coding
       caused a substantial performance problem for applications that made
       heavy use of "DISCARD ALL".
     - Fix PL/pgSQL to not treat INTO after "INSERT" as an INTO-variables
       clause anywhere in the string, not only at the start; in
       particular, don't fail for "INSERT INTO" within "CREATE RULE".
     - Clean up PL/pgSQL error status variables fully at block exit.
       This is not a problem for PL/pgSQL itself, but the omission could
       cause the PL/pgSQL Debugger to crash while examining the state of a
       function.
     - Add MUST (Mauritius Island Summer Time) to the default list of
       known timezone abbreviations.
Files: 
 0ec7f570594d670cf0b0775061807576 1303 misc optional postgresql-8.3_8.3.7-0ubuntu8.04.dsc
 e2d05c1d83cee3831736644bb022c5dd 62064 misc optional postgresql-8.3_8.3.7-0ubuntu8.04.diff.gz
Original-Maintainer: Martin Pitt <mpitt at debian.org>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknJ6EoACgkQDecnbV4Fd/KfEwCdHkpUnToN79+0tYN/Zi2UcvsK
GBgAnAv2bkOPSur8AxlKq5UQHLlLGxmK
=ToXz
-----END PGP SIGNATURE-----


More information about the Hardy-changes mailing list