postgresql-8.2 8.2.9-0ubuntu0.7.10 source package in Ubuntu

Changelog

postgresql-8.2 (8.2.9-0ubuntu0.7.10) gutsy-proposed; urgency=low

  * New upstream bug fix release (note that 8.2.8 was never officially
    released due to the discovery of another major bug):
    - Make pg_get_ruledef() parenthesize negative constants.
      Before this fix, a negative constant in a view or rule might be
      dumped as, say, -42::integer, which is subtly incorrect: it should
      be (-42)::integer due to operator precedence rules. Usually this
      would make little difference, but it could interact with another
      recent patch to cause PostgreSQL to reject what had been a valid
      "SELECT DISTINCT" view query. Since this could result in pg_dump
      output failing to reload, it is being treated as a high-priority
      fix.
    - 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 pg_get_ruledef() to show the alias, if any, attached to the
      target table of an "UPDATE" or "DELETE".
    - Fix GIN bug that could result in a too many LWLocks taken failure.
    - Avoid possible crash when decompressing corrupted data.
    - Repair two places where SIGTERM exit of a backend could leave
      corrupted state in shared memory.
    - Fix conversions between ISO-8859-5 and other encodings to handle
      Cyrillic "Yo" characters (e and E with two dots).
    - Fix several datatype input functions, notably array_in(), 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 broken GiST comparison function for "contrib/tsearch2"'s
      tsquery type.
    - Fix possible crashes in "contrib/cube" functions.
    - Fix core dump in "contrib/xml2"'s xpath_table() function when the
      input query returns a NULL value.
   (LP: #238587)

 -- Martin Pitt <email address hidden>   Mon, 09 Jun 2008 17:32:57 +0200