lp:ubuntu/gutsy-proposed/postgresql-8.2

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

19. By Martin Pitt on 2008-11-04

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

18. By Martin Pitt on 2008-06-09

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

17. By Martin Pitt on 2008-03-18

* New upstream bug fix release: (LP: #203734)
  - 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 Debian #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.
* Remove debian/patches/00upstream-clauseless-joins-regression.patch,
  upstream now.

16. By Martin Pitt on 2008-01-05

* New upstream security/bugfix release:
  - Prevent functions in indexes from executing with the privileges of
    the user running "VACUUM", "ANALYZE", etc. "SET ROLE" is now forbidden
    within a SECURITY DEFINER context. [CVE-2007-6600]
  - Suitably crafted regular-expression patterns could cause crashes,
    infinite or near-infinite looping, and/or massive memory
    consumption, all of which pose denial-of-service hazards for
    applications that accept regex search patterns from untrustworthy
    sources. [CVE-2007-4769, CVE-2007-4772, CVE-2007-6067]
  - Require non-superusers who use "/contrib/dblink" to use only
    password authentication, as a security measure.
    The fix that appeared for this in 8.2.5 was incomplete, as it
    plugged the hole for only some "dblink" functions. [CVE-2007-6601,
    CVE-2007-3278]
  - Fix bugs in WAL replay for GIN indexes.
  - Fix GIN index build to work properly when maintenance_work_mem is
    4GB or more.
  - Improve planner's handling of LIKE/regex estimation in non-C
    locales.
  - Fix planning-speed problem for deep outer-join nests, as well as
    possible poor choice of join order.
  - Fix planner failure in some cases of WHERE false AND var IN (SELECT
    ...).
  - Make "CREATE TABLE ... SERIAL" and "ALTER SEQUENCE ... OWNED BY"
    not change the currval() state of the sequence.
  - Preserve the tablespace and storage parameters of indexes that are
    rebuilt by "ALTER TABLE ... ALTER COLUMN TYPE".
  - Make archive recovery always start a new WAL timeline, rather than
    only when a recovery stop time was used. This avoids a corner-case risk
    of trying to overwrite an existing archived copy of the last WAL
    segment, and seems simpler and cleaner than the original definition.
  - Make "VACUUM" not use all of maintenance_work_mem when the table is
    too small for it to be useful.
  - Fix potential crash in translate() when using a multibyte database
    encoding.
  - Make corr() return the correct result for negative correlation
    values.
  - Fix overflow in extract(epoch from interval) for intervals
    exceeding 68 years.
  - Fix PL/Perl to not fail when a UTF-8 regular expression is used in
    a trusted function.
  - Fix PL/Python to work correctly with Python 2.5 on 64-bit machines
    (Marko Kreen)
  - Fix PL/Python to not crash on long exception messages.
  - Fix pg_dump to correctly handle inheritance child tables that have
    default expressions different from their parent's.
  - Fix libpq crash when PGPASSFILE refers to a file that is not a
    plain file.
  - ecpg parser fixes.
  - Make "contrib/tablefunc"'s crosstab() handle NULL rowid as a
    category in its own right, rather than crashing.
  - Fix tsvector and tsquery output routines to escape backslashes
    correctly. (LP: #146382)
  - Fix crash of to_tsvector() on huge input strings.
* Drop debian/patches/00upstream-tsearch2-compareWORD.patch, upstream.

15. By Martin Pitt on 2007-09-28

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

14. By Martin Pitt on 2007-09-16

* New upstream bugfix release:
  - Require non-superusers who use "/contrib/dblink" to use only
    password authentication, as a security measure.
    [CVE-2007-3278, CVE-2007-3280]
  - Fix ALTER DOMAIN ADD CONSTRAINT for cases involving domains over
    domains.
  - Make "CREATE DOMAIN ... DEFAULT NULL" work properly.
  - Fix some planner problems with outer joins, notably poor size
    estimation for t1 LEFT JOIN t2 WHERE t2.col IS NULL.
  - Allow the interval data type to accept input consisting only of
    milliseconds or microseconds.
  - Allow timezone name to appear before the year in timestamp input.
  - Fixes for GIN indexes used by "/contrib/tsearch2".
  - Speed up rtree index insertion.
  - Fix excessive logging of SSL error messages.
  - Fix logging so that log messages are never interleaved when using
    the syslogger process.
  - Fix crash when log_min_error_statement logging runs out of memory.
  - Fix incorrect handling of some foreign-key corner cases.
  - Fix stddev_pop(numeric) and var_pop(numeric).
  - Prevent "REINDEX" and "CLUSTER" from failing due to attempting to
    process temporary tables of other sessions.
  - Restrict "/contrib/pgstattuple" functions to superusers, for
    security reasons.
  - Do not let "/contrib/intarray" try to make its GIN opclass the
    default (this caused problems at dump/restore).
* Remove debian/patches/00upstream-01-polymorphic-functions.patch: Upstream
  now.

13. By Martin Pitt on 2007-08-04

* Urgency medium since the dpkg bug above is nasty and I want this fixed in
  testing ASAP.
* debian/postgresql-8.2.postinst: Work around dpkg bug #435938 by manually
  doing the timezone symlink transition. Closes: #430524
* debian/rules: Make binary-arch idempotent if test suite fails.
  Closes: #431565

12. By Martin Pitt on 2007-06-23

* debian/control: Remove some unnecessary build depends. Closes: #424010
* debian/postgresql-8.2.install: Actually install the "timezone" symlink,
  not the dereferenced files.
* Add debian/patches/12-m32r-tas.patch:
  - Support m32r architecture, thanks to Kazuhiro Inaoka for the initial
    patch.
  - Backported from CVS head:
    http://archives.postgresql.org/pgsql-committers/2007-05/msg00065.php
  - Closes: #419267
* Add debian/patches/00upstream-01-polymorphic-functions.patch:
  - Fix breakage of polymorphic SQL functions (regression in 8.2.4), add
    test cases.
  - Patch taken from upstream CVS:
    http://archives.postgresql.org/pgsql-committers/2007-05/msg00010.php
  - Closes: #430347
* debian/control: Fix libpq-dev Depends: line: ${Source-Version} ->
  ${binary:Version}.

11. By Martin Pitt on 2007-04-20

* New upstream security/bug fix release:
  - Support explicit placement of the temporary-table schema within
    search_path, and disable searching it for functions and operators.
    This is needed to allow a security-definer function to set a truly
    secure value of search_path. Without it, an unprivileged SQL user
    can use temporary objects to execute code with the privileges of
    the security-definer function (CVE-2007-2138). See "CREATE
    FUNCTION" for more information.
  - Fix to_char() so it properly upper/lower cases localized day or
    month names.
  - "/contrib/tsearch2" crash fixes.
  - Require "COMMIT PREPARED" to be executed in the same database as
    the transaction was prepared in.
  - New traditional (Taiwan) Chinese FAQ.
  - Prevent the statistics collector from writing to disk too
    frequently.
  - Fix potential-data-corruption bug in how "VACUUM FULL" handles
    "UPDATE" chains.
  - Fix bug in domains that use array types.
  - Fix "pg_dump" so it can dump a serial column's sequence using "-t"
    when not also dumping the owning table.
  - Planner fixes, including improving outer join and bitmap scan
    selection logic.
  - Fix possible wrong answers or crash when a PL/pgSQL function tries
    to RETURN from within an EXCEPTION block.
  - Fix PANIC during enlargement of a hash index.
* debian/patches/04-timezone-symlinks.patch: Adapt to slightly changed
  Makefile of 8.2.4.
* Remove debian/patches/12-vacuum-cycle-hang.patch: Fixed upstream.
* debian/postgresql-8.2.postrm: Fix bashism.

10. By Martin Pitt on 2007-04-04

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