Author: Martin Pitt
Revision Date: 2008-04-22 14:11:57 UTC

Bump build dependency libpq-dev to a version which depends on libpq5, to
unbreak backports. Thanks to Gerfried Fuchs! (Closes: #474363)

Author: Martin Pitt
Revision Date: 2008-03-16 11:57:26 UTC

* New upstream bug fix release:
  - Repair potential deadlock between concurrent "VACUUM FULL"
    operations on different system catalogs.
  - Fix longstanding "LISTEN"/"NOTIFY" race condition.
  - 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.
  - Disallow dropping a temporary table within a prepared transaction
    This was correctly disallowed by 8.1, but the check was
    inadvertently broken in 8.2.
  - Fix rare crash when an error occurs during a query using a hash
    index.
  - Fix memory leaks in certain usages of set-returning functions.
  - Fix input of datetime values for February 29 in years BC.
  - Fix "unrecognized node type" error in some variants of "ALTER
    OWNER".
  - Ensure pg_stat_activity.waiting flag is cleared when a lock wait is
    aborted.
  - Fix pg_ctl to correctly extract the postmaster's port number from
    command-line options.(See #358546)
  - Use "-fwrapv" to defend against possible misoptimization in recent
    gcc versions.
  - Correctly enforce statement_timeout values longer than INT_MAX
    microseconds (about 35 minutes).
  - Fix "unexpected PARAM_SUBLINK ID" planner error when
    constant-folding simplifies a sub-select.
  - Fix logical errors in constraint-exclusion handling of IS NULL and
    NOT expressions.
  - Fix another cause of "failed to build any N-way joins" planner
    errors.
  - Fix incorrect constant propagation in outer-join planning.
  - Fix display of constant expressions in ORDER BY and GROUP BY.
  - Fix libpq to handle NOTICE messages correctly during COPY OUT.
* debian/watch: Update for currently working mirror. (Closes: #462823)

Author: Martin Pitt
Revision Date: 2008-11-04 21:22:42 UTC

* New upstream bug fix release 8.2.11: (LP: #293758)
  - Fix GiST index corruption due to marking the wrong index entry
    "dead" after a deletion. This would result in index searches failing to
    find rows they should have found.
  - Fix backend crash when the client encoding cannot represent a
    localized error message.
  - Fix possible crash when deeply nested functions are invoked from a
    trigger.
  - Improve optimization of "expression" IN ("expression-list") queries.
    Cases in which there are query variables on the right-hand side had
    been handled less efficiently in 8.2.x and 8.3.x than in prior
    versions. The fix restores 8.1 behavior for such cases.
  - Fix mis-expansion of rule queries when a sub-SELECT appears in a
    function call in FROM, a multi-row VALUES list, or a RETURNING list.
    The usual symptom of this problem is an "unrecognized node type"
    error.
  - Fix memory leak during rescan of a hashed aggregation plan.
  - Ensure an error is reported when a newly-defined PL/pgSQL trigger
    function is invoked as a normal function.
  - Prevent possible collision of relfilenode numbers when moving a
    table to another tablespace with "ALTER SET TABLESPACE".
  - Fix incorrect tsearch2 headline generation when single query item
    matches first word of text.
  - Fix improper display of fractional seconds in interval values when
    using a non-ISO datestyle.
  - Ensure SPI_getvalue and SPI_getbinval behave correctly when the
    passed tuple and tuple descriptor have different numbers of columns.
    This situation is normal when a table has had columns added or
    removed, but these two functions didn't handle it properly. The
    only likely consequence is an incorrect error indication.
  - Fix ecpg's parsing of "CREATE ROLE".
  - Fix recent breakage of pg_ctl restart.
* 03-gettext-domains.patch: Unfuzz for new release.

Author: Martin Pitt
Revision Date: 2008-11-04 21:22:42 UTC

* New upstream bug fix release 8.2.11: (LP: #293758)
  - Fix GiST index corruption due to marking the wrong index entry
    "dead" after a deletion. This would result in index searches failing to
    find rows they should have found.
  - Fix backend crash when the client encoding cannot represent a
    localized error message.
  - Fix possible crash when deeply nested functions are invoked from a
    trigger.
  - Improve optimization of "expression" IN ("expression-list") queries.
    Cases in which there are query variables on the right-hand side had
    been handled less efficiently in 8.2.x and 8.3.x than in prior
    versions. The fix restores 8.1 behavior for such cases.
  - Fix mis-expansion of rule queries when a sub-SELECT appears in a
    function call in FROM, a multi-row VALUES list, or a RETURNING list.
    The usual symptom of this problem is an "unrecognized node type"
    error.
  - Fix memory leak during rescan of a hashed aggregation plan.
  - Ensure an error is reported when a newly-defined PL/pgSQL trigger
    function is invoked as a normal function.
  - Prevent possible collision of relfilenode numbers when moving a
    table to another tablespace with "ALTER SET TABLESPACE".
  - Fix incorrect tsearch2 headline generation when single query item
    matches first word of text.
  - Fix improper display of fractional seconds in interval values when
    using a non-ISO datestyle.
  - Ensure SPI_getvalue and SPI_getbinval behave correctly when the
    passed tuple and tuple descriptor have different numbers of columns.
    This situation is normal when a table has had columns added or
    removed, but these two functions didn't handle it properly. The
    only likely consequence is an incorrect error indication.
  - Fix ecpg's parsing of "CREATE ROLE".
  - Fix recent breakage of pg_ctl restart.
* 03-gettext-domains.patch: Unfuzz for new release.

Author: Martin Pitt
Revision Date: 2007-09-28 15:12:33 UTC

* Upload bzr head to Gutsy to get the fix below quickly.
* Add debian/patches/00upstream-tsearch2-compareWORD.patch:
  - Fix tsearch2's compareWORD() function to return 0 on identical strings.
    This avoids endless loops for situations where identical strings appear
    in sort lists (which Should Not Happen™, but do anyway).
  - Patch taken from upstream CVS:
    http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/tsvector.c?r1=1.26&r2=1.26.2.1
  - Thanks to Stuart Bishop for finding the bug and providing a reproducer.
  - (LP: #141637)

Author: Martin Pitt
Revision Date: 2008-06-09 17:44:02 UTC

* 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)

Author: Martin Pitt
Revision Date: 2008-01-11 16:29:39 UTC

* Upload 8.2.6 into gutsy-security.
* Add debian/patches/00upstream-clauseless-joins-regression.patch:
  - Fix a regression of 8.2.6 wrt. large clauseless joins.
  - Taken from upstream CVS:
    http://archives.postgresql.org/pgsql-committers/2008-01/msg00164.php

Author: Martin Pitt
Revision Date: 2008-06-09 17:44:02 UTC

* 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)

Author: Martin Pitt
Revision Date: 2008-01-11 16:35:02 UTC

* Upload 8.2.6 into feisty-security.
* Add debian/patches/00upstream-clauseless-joins-regression.patch:
  - Fix a regression of 8.2.6 wrt. large clauseless joins.
  - Taken from upstream CVS:
    http://archives.postgresql.org/pgsql-committers/2008-01/msg00164.php

Author: Martin Pitt
Revision Date: 2007-04-04 12:09:37 UTC

debian/rules: Do not FTBFS on failed test suite on sparc. sparc throws a
'floating point exception' instead of a 'division by zero' error, which is
fine, but differs from expected string output. Closes: #417160

Author: Martin Pitt
Revision Date: 2007-05-23 13:02:51 UTC

Automated backport upload; no source changes.