lp:ubuntu/oneiric/postgresql-8.4

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

24. By Martin Pitt on 2011-05-22

* debian/postgresql-8.4.postrm: Clean up pg_ctl.conf on purge.
* debian/control, debian/rules: Drop usage of pycentral. We don't ship any
  Python extension/module, so we don't need a python helper at all.
  (Closes: #616948)
* Add 16-cmsgcred-size.patch: Fix size of struct cmsgcred to fix ident
  authentication on kFreeBSD 64 bit. Thanks to Petr Salinger for the patch!
  (Closes: #612888)

23. By Colin Watson on 2011-05-12

Rebuild for Perl 5.12.

22. By Martin Pitt on 2011-04-20

Priority medium due to data-loss pg_upgrade bug.

[ Martin Pitt ]
* New upstream bug fix release:
  - If your installation was upgraded from a previous major release by
    running pg_upgrade, you should take action to prevent possible data loss
    due to a now-fixed bug in pg_upgrade. The recommended solution is to run
    "VACUUM FREEZE" on all TOAST tables. More information is available at
    http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.
  - Fix pg_upgrade's handling of TOAST tables.
    This error poses a significant risk of data loss for installations
    that have been upgraded with pg_upgrade. This patch corrects the
    problem for future uses of pg_upgrade, but does not in itself cure
    the issue in installations that have been processed with a buggy
    version of pg_upgrade.
  - Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set"
    warning.
  - Disallow including a composite type in itself.
  - Avoid potential deadlock during catalog cache initialization.
  - Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling
    when there was a concurrent update to the target tuple.
  - Disallow "DROP TABLE" when there are pending deferred trigger
    events for the table.
    Formerly the "DROP" would go through, leading to "could not open
    relation with OID nnn" errors when the triggers were eventually
    fired.
  - Prevent crash triggered by constant-false WHERE conditions during
    GEQO optimization.
  - Improve planner's handling of semi-join and anti-join cases.
  - Fix selectivity estimation for text search to account for NULLs.
  - Improve PL/pgSQL's ability to handle row types with dropped columns.
  - Fix PL/Python memory leak involving array slices.
  - Fix pg_restore to cope with long lines (over 1KB) in TOC files.
  - Put in more safeguards against crashing due to division-by-zero
    with overly enthusiastic compiler optimization. (Closes: #616180)
* debian/control: Stop building the versionless metapackages and client-side
  libraries, they are built by postgresql-9.0 now. Add libpq-dev build
  dependency.
* debian/rules: Drop check for uninstalled files, since it'd now break the
  build due to the uninstalled libraries.

[ Matthias Klose ]
* Add 15-bool-altivec.patch: Fix definition of bool on __APPLE_ALTIVEC__
  architecture (ppc64).

21. By Martin Pitt on 2011-04-20

* New upstream bug fix release: (LP: #767165)
  - If your installation was upgraded from a previous major release by
    running pg_upgrade, you should take action to prevent possible data loss
    due to a now-fixed bug in pg_upgrade. The recommended solution is to run
    "VACUUM FREEZE" on all TOAST tables. More information is available at
    http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix.
  - Fix pg_upgrade's handling of TOAST tables.
    This error poses a significant risk of data loss for installations
    that have been upgraded with pg_upgrade. This patch corrects the
    problem for future uses of pg_upgrade, but does not in itself cure
    the issue in installations that have been processed with a buggy
    version of pg_upgrade.
  - Suppress incorrect "PD_ALL_VISIBLE flag was incorrectly set"
    warning.
  - Disallow including a composite type in itself.
  - Avoid potential deadlock during catalog cache initialization.
  - Fix dangling-pointer problem in BEFORE ROW UPDATE trigger handling
    when there was a concurrent update to the target tuple.
  - Disallow "DROP TABLE" when there are pending deferred trigger
    events for the table.
    Formerly the "DROP" would go through, leading to "could not open
    relation with OID nnn" errors when the triggers were eventually
    fired.
  - Prevent crash triggered by constant-false WHERE conditions during
    GEQO optimization.
  - Improve planner's handling of semi-join and anti-join cases.
  - Fix selectivity estimation for text search to account for NULLs.
  - Improve PL/pgSQL's ability to handle row types with dropped columns.
  - Fix PL/Python memory leak involving array slices.
  - Fix pg_restore to cope with long lines (over 1KB) in TOC files.
  - Put in more safeguards against crashing due to division-by-zero
    with overly enthusiastic compiler optimization. (Closes: #616180)

20. By Matthias Klose on 2011-03-15

Fix definition of bool on ppc64.

19. By Martin Pitt on 2011-02-01

* New upstream security/bug fix release:
  - Fix buffer overrun in "contrib/intarray"'s input function for the
    query_int type.
    This bug is a security risk since the function's return address
    could be overwritten. Thanks to Apple Inc's security team for
    reporting this issue and supplying the fix. (CVE-2010-4015)
  - Avoid failures when "EXPLAIN" tries to display a simple-form CASE
    expression.
    If the CASE's test expression was a constant, the planner could
    simplify the CASE into a form that confused the expression-display
    code, resulting in "unexpected CASE WHEN clause" errors.
  - Fix assignment to an array slice that is before the existing range
    of subscripts.
    If there was a gap between the newly added subscripts and the first
    pre-existing subscript, the code miscalculated how many entries
    needed to be copied from the old array's null bitmap, potentially
    leading to data corruption or crash.
  - Avoid unexpected conversion overflow in planner for very distant
    date values.
    The date type supports a wider range of dates than can be
    represented by the timestamp types, but the planner assumed it
    could always convert a date to timestamp with impunity.
  - Fix pg_restore's text output for large objects (BLOBs) when
    standard_conforming_strings is on.
    Although restoring directly to a database worked correctly, string
    escaping was incorrect if pg_restore was asked for SQL text output
    and standard_conforming_strings had been enabled in the source
    database.
  - Fix erroneous parsing of tsquery values containing ... &
    !(subexpression) | ... .
    Queries containing this combination of operators were not executed
    correctly. The same error existed in "contrib/intarray"'s query_int
    type and "contrib/ltree"'s ltxtquery type.
  - Fix bug in "contrib/seg"'s GiST picksplit algorithm.
    This could result in considerable inefficiency, though not actually
    incorrect answers, in a GiST index on a seg column. If you have
    such an index, consider "REINDEX"ing it after installing this
    update. (This is identical to the bug that was fixed in
    "contrib/cube" in the previous update.)

18. By Martin Pitt on 2010-12-18

* New upstream bug fix release:
  - Force the default wal_sync_method to be fdatasync on Linux.
    The default on Linux has actually been fdatasync for many years,
    but recent kernel changes caused PostgreSQL to choose open_datasync
    instead. This choice did not result in any performance improvement,
    and caused outright failures on certain filesystems, notably ext4
    with the data=journal mount option.
  - Fix assorted bugs in WAL replay logic for GIN indexes.
    This could result in "bad buffer id: 0" failures or corruption of
    index contents during replication.
  - Fix recovery from base backup when the starting checkpoint WAL
    record is not in the same WAL segment as its redo point.
  - Fix persistent slowdown of autovacuum workers when multiple workers
    remain active for a long time.
    The effective vacuum_cost_limit for an autovacuum worker could drop
    to nearly zero if it processed enough tables, causing it to run
    extremely slowly.
  - Add support for detecting register-stack overrun on IA64.
    The IA64 architecture has two hardware stacks. Full prevention of
    stack-overrun failures requires checking both.
  - Add a check for stack overflow in copyObject().
    Certain code paths could crash due to stack overflow given a
    sufficiently complex query.
  - Fix detection of page splits in temporary GiST indexes.
    It is possible to have a "concurrent" page split in a temporary
    index, if for example there is an open cursor scanning the index
    when an insertion is done. GiST failed to detect this case and
    hence could deliver wrong results when execution of the cursor
    continued.
  - Fix error checking during early connection processing.
    The check for too many child processes was skipped in some cases,
    possibly leading to postmaster crash when attempting to add the new
    child process to fixed-size arrays.
  - Improve efficiency of window functions.
    Certain cases where a large number of tuples needed to be read in
    advance, but work_mem was large enough to allow them all to be held
    in memory, were unexpectedly slow. percent_rank(), cume_dist() and
    ntile() in particular were subject to this problem.
  - Avoid memory leakage while "ANALYZE"'ing complex index expressions.
  - Ensure an index that uses a whole-row Var still depends on its
    table.
    An index declared like create index i on t (foo(t.-)) would not
    automatically get dropped when its table was dropped.
  - Do not "inline" a SQL function with multiple OUT parameters.
    This avoids a possible crash due to loss of information about the
    expected result rowtype.
  - Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
    attached to the VALUES part of INSERT ... VALUES.
  - Fix constant-folding of COALESCE() expressions.
    The planner would sometimes attempt to evaluate sub-expressions
    that in fact could never be reached, possibly leading to unexpected
    errors.
  - Fix postmaster crash when connection acceptance (accept() or one of
    the calls made immediately after it) fails, and the postmaster was
    compiled with GSSAPI support.
  - Fix missed unlink of temporary files when log_temp_files is active.
    If an error occurred while attempting to emit the log message, the
    unlink was not done, resulting in accumulation of temp files.
  - Add print functionality for InhRelation nodes.
    This avoids a failure when debug_print_parse is enabled and certain
    types of query are executed.
  - Fix incorrect calculation of distance from a point to a horizontal
    line segment.
    This bug affected several different geometric distance-measurement
    operators.
  - Fix incorrect calculation of transaction status in ecpg.
  - Fix PL/pgSQL's handling of "simple" expressions to not fail in
    recursion or error-recovery cases.
  - Fix PL/Python's handling of set-returning functions.
    Attempts to call SPI functions within the iterator generating a set
    result would fail.
  - Fix bug in "contrib/cube"'s GiST picksplit algorithm.
    This could result in considerable inefficiency, though not actually
    incorrect answers, in a GiST index on a cube column. If you have
    such an index, consider "REINDEX"ing it after installing this
    update.
  - Don't emit "identifier will be truncated" notices in
    "contrib/dblink" except when creating new connections.
  - Fix potential coredump on missing public key in "contrib/pgcrypto".
  - Fix memory leak in "contrib/xml2"'s XPath query functions.

17. By Matthias Klose on 2010-12-09

Rebuild with python 2.7 as the python default.

16. By Martin Pitt on 2010-11-17

debian/control: Build against libedit instead of libreadline. We can't
simultaneously link against readline (GPL) and libssl (incompatible with
GPL). (Closes: #603598)

15. By Martin Pitt on 2010-10-05

* Urgency medium, since this fixes a security bug (but also a lot of other
  bugs, it's not a pinpointed patch).
* New upstream security/bug fix update:
  - Use a separate interpreter for each calling SQL userid in PL/Perl
    and PL/Tcl.
    This change prevents security problems that can be caused by
    subverting Perl or Tcl code that will be executed later in the same
    session under another SQL user identity (for example, within a
    SECURITY DEFINER function). Most scripting languages offer numerous
    ways that that might be done, such as redefining standard functions
    or operators called by the target function. Without this change,
    any SQL user with Perl or Tcl language usage rights can do
    essentially anything with the SQL privileges of the target
    function's owner.
    The cost of this change is that intentional communication among
    Perl and Tcl functions becomes more difficult. To provide an escape
    hatch, PL/PerlU and PL/TclU functions continue to use only one
    interpreter per session. This is not considered a security issue
    since all such functions execute at the trust level of a database
    superuser already.
    It is likely that third-party procedural languages that claim to
    offer trusted execution have similar security issues. We advise
    contacting the authors of any PL you are depending on for
    security-critical purposes.
    Our thanks to Tim Bunce for pointing out this issue
    (CVE-2010-3433).
  - Prevent possible crashes in pg_get_expr() by disallowing it from
    being called with an argument that is not one of the system catalog
    columns it's intended to be used with.
  - Fix incorrect placement of placeholder evaluation.
    This bug could result in query outputs being non-null when they
    should be null, in cases where the inner side of an outer join is a
    sub-select with non-strict expressions in its output list.
  - Fix possible duplicate scans of UNION ALL member relations.
  - Fix "cannot handle unplanned sub-select" error.
    This occurred when a sub-select contains a join alias reference
    that expands into an expression containing another sub-select.
  - Fix mishandling of whole-row Vars that reference a view or
    sub-select and appear within a nested sub-select.
  - Fix mishandling of cross-type IN comparisons.
    This could result in failures if the planner tried to implement an
    IN join with a sort-then-unique-then-plain-join plan.
  - Fix computation of "ANALYZE" statistics for tsvector columns.
    The original coding could produce incorrect statistics, leading to
    poor plan choices later.
  - Improve planner's estimate of memory used by array_agg(),
    string_agg(), and similar aggregate functions.
    The previous drastic underestimate could lead to out-of-memory
    failures due to inappropriate choice of a hash-aggregation plan.
  - Fix failure to mark cached plans as transient.
    If a plan is prepared while "CREATE INDEX CONCURRENTLY" is in
    progress for one of the referenced tables, it is supposed to be
    re-planned once the index is ready for use. This was not happening
    reliably.
  - Reduce PANIC to ERROR in some occasionally-reported btree failure
    cases, and provide additional detail in the resulting error
    messages.
    This should improve the system's robustness with corrupted indexes.
  - Fix incorrect search logic for partial-match queries with GIN
    indexes.
    Cases involving AND/OR combination of several GIN index conditions
    didn't always give the right answer, and were sometimes much slower
    than necessary.
  - Prevent show_session_authorization() from crashing within
    autovacuum processes.
  - Defend against functions returning setof record where not all the
    returned rows are actually of the same rowtype.
  - Fix possible corruption of pending trigger event lists during
    subtransaction rollback.
    This could lead to a crash or incorrect firing of triggers.
  - Fix possible failure when hashing a pass-by-reference function
    result.
  - Improve merge join's handling of NULLs in the join columns.
    A merge join can now stop entirely upon reaching the first NULL, if
    the sort order is such that NULLs sort high.
  - Take care to fsync the contents of lockfiles (both "postmaster.pid"
    and the socket lockfile) while writing them.
    This omission could result in corrupted lockfile contents if the
    machine crashes shortly after postmaster start. That could in turn
    prevent subsequent attempts to start the postmaster from
    succeeding, until the lockfile is manually removed.
  - Avoid recursion while assigning XIDs to heavily-nested
    subtransactions.
    The original coding could result in a crash if there was limited
    stack space.
  - Avoid holding open old WAL segments in the walwriter process.
    The previous coding would prevent removal of no-longer-needed
    segments.
  - Fix log_line_prefix's %i escape, which could produce junk early in
    backend startup.
  - Prevent misinterpretation of partially-specified relation options
    for TOAST tables.
    In particular, fillfactor would be read as zero if any other
    reloption had been set for the table, leading to serious bloat.
  - Fix inheritance count tracking in "ALTER TABLE ... ADD CONSTRAINT"
  - Fix possible data corruption in "ALTER TABLE ... SET TABLESPACE"
    when archiving is enabled.
  - Allow "CREATE DATABASE" and "ALTER DATABASE ... SET TABLESPACE" to
    be interrupted by query-cancel.
  - Improve "CREATE INDEX"'s checking of whether proposed index
    expressions are immutable.
  - Fix "REASSIGN OWNED" to handle operator classes and families.
  - Fix possible core dump when comparing two empty tsquery values.
  - Fix LIKE's handling of patterns containing % followed by _.
    We've fixed this before, but there were still some
    incorrectly-handled cases.
  - Re-allow input of Julian dates prior to 0001-01-01 AD.
    Input such as 'J100000'::date worked before 8.4, but was
    unintentionally broken by added error-checking.
  - Fix PL/pgSQL to throw an error, not crash, if a cursor is closed
    within a FOR loop that is iterating over that cursor.
  - In PL/Python, defend against null pointer results from
    PyCObject_AsVoidPtr and PyCObject_FromVoidPtr.
  - In libpq, fix full SSL certificate verification for the case where
    both host and hostaddr are specified.
  - Make psql recognize "DISCARD ALL" as a command that should not be
    encased in a transaction block in autocommit-off mode.
  - Fix some issues in pg_dump's handling of SQL/MED objects.
    Notably, pg_dump would always fail if run by a non-superuser, which
    was not intended.
  - Improve pg_dump and pg_restore's handling of non-seekable archive
    files.
    This is important for proper functioning of parallel restore.
  - Improve parallel pg_restore's ability to cope with selective
    restore (-L option).
    The original code tended to fail if the -L file commanded a
    non-default restore ordering.
  - Fix ecpg to process data from RETURNING clauses correctly.
  - Fix some memory leaks in ecpg.
  - Improve "contrib/dblink"'s handling of tables containing dropped
    columns.
  - Fix connection leak after "duplicate connection name" errors in
    "contrib/dblink".
  - Fix "contrib/dblink" to handle connection names longer than 62
    bytes correctly.
  - Add hstore(text, text) function to "contrib/hstore".
    This function is the recommended substitute for the now-deprecated
    => operator. It was back-patched so that future-proofed code can be
    used with older server versions. Note that the patch will be
    effective only after "contrib/hstore" is installed or reinstalled
    in a particular database. Users might prefer to execute the "CREATE
    FUNCTION" command by hand, instead.
  - Update build infrastructure and documentation to reflect the source
    code repository's move from CVS to Git.
* debian/postgresql-8.4.preinst: Add missing debhelper token.
* debian/control: Bump Standards-Version to 3.9.1 (no changes necessary).