postgresql-8.1 8.1.13-0ubuntu0.6.06 source package in Ubuntu

Changelog

postgresql-8.1 (8.1.13-0ubuntu0.6.06) dapper-proposed; urgency=low

  * New upstream bugfix release (please note that 8.1.12 was never released,
    due to the discovery of another major bug):
     - Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend.
       This oversight could lead to problems if the aggregate was later
       involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
     - Fix "ALTER TABLE ADD COLUMN ... PRIMARY KEY" so that the new column
       is correctly checked to see if it's been initialized to all
       non-nulls. Previous versions neglected to check this requirement at
       all.
     - Fix possible "CREATE TABLE" failure when inheriting the "same"
       constraint from multiple parent relations that inherited that
       constraint from a common ancestor.
     - Fix conversions between ISO-8859-5 and other encodings to handle
       Cyrillic "Yo" characters (e and E with two dots).
     - Fix a few datatype input functions that were allowing unused bytes
       in their results to contain uninitialized, unpredictable values.
       This could lead to failures in which two apparently identical
       literal values were not seen as equal, resulting in the parser
       complaining about unmatched ORDER BY and DISTINCT expressions.
     - Fix a corner case in regular-expression substring matching.
     - Fix incorrect result from ecpg's PGTYPEStimestamp_sub() function.
     - Fix core dump in "contrib/xml2"'s xpath_table() function when the
       input query returns a NULL value.
     - Fix longstanding "LISTEN"/"NOTIFY" race condition.
       In rare cases a session that had just executed a "LISTEN" might not
       get a notification, even though one would be expected because the
       concurrent transaction executing "NOTIFY" was observed to commit
       later.
       A side effect of the fix is that a transaction that has executed a
       not-yet-committed "LISTEN" command will not see any row in
       pg_listener for the "LISTEN", should it choose to look; formerly it
       would have. This behavior was never documented one way or the
       other, but it is possible that some applications depend on the old
       behavior.
     - Disallow "LISTEN" and "UNLISTEN" within a prepared transaction.
       This was formerly allowed but trying to do it had various
       unpleasant consequences, notably that the originating backend could
       not exit as long as an "UNLISTEN" remained uncommitted.
     - Fix rare crash when an error occurs during a query using a hash
       index.
     - Fix input of datetime values for February 29 in years BC.
       The former coding was mistaken about which years were leap years.
     - Fix "unrecognized node type" error in some variants of "ALTER
       OWNER".
     - Fix pg_ctl to correctly extract the postmaster's port number from
       command-line options.
       Previously, pg_ctl start -w could try to contact the postmaster on
       the wrong port, leading to bogus reports of startup failure.
     - Fix display of constant expressions in ORDER BY and GROUP BY.
       An explictly casted constant would be shown incorrectly. This could
       for example lead to corruption of a view definition during dump and
       reload.
     - Fix libpq to handle NOTICE messages correctly during COPY OUT.
       This failure has only been observed to occur when a user-defined
       datatype's output routine issues a NOTICE, but there is no
       guarantee it couldn't happen due to other causes.
     (LP: #238587)

 -- Martin Pitt <email address hidden>   Mon, 09 Jun 2008 19:09:25 +0200