postgresql-9.1 (9.1.13-1) unstable; urgency=medium

  * New upstream release:
    - Fix memory leak in PL/Perl when returning a composite result, including
      multiple-OUT-parameter cases.
  * Bump Standards-Version to 3.9.5. No changes necessary.

 -- Martin Pitt <mpitt@debian.org>  Tue, 18 Mar 2014 10:18:13 +0100

postgresql-9.1 (9.1.12-1) unstable; urgency=medium

  * New upstream release: No effective changes for PL/Perl, the version must
    just be higher than the one in wheezy.

 -- Martin Pitt <mpitt@debian.org>  Thu, 20 Feb 2014 08:02:45 -0800

postgresql-9.1 (9.1.11-2) unstable; urgency=low

  * Branch off "jessie" for the reduction to PL/Perl, keep "trunk" for the
    full builds on apt.postgresql.org. Update Vcs-*.
  * Drop all binary packages except for postgresql-plperl-9.1.  Version 9.1 is
    obsolete and not supported in Jessie any more. However,
    postgresql-plperl-9.1 from Wheezy is not installable in Jessie any more
    due to the different Perl version, so we need a postgresql-plperl-9.1
    built against libperl5.18 so that you can upgrade your existing 9.1
    clusters to 9.3. Drop unnecessary build dependencies and disable the
    optional features to speed up the build.
  * Drop autopkgtest, we can't test this package standalone within wheezy.

 -- Martin Pitt <mpitt@debian.org>  Tue, 17 Dec 2013 11:19:04 +0100

postgresql-9.1 (9.1.11-1) unstable; urgency=low

  [ Martin Pitt ]
  * Stop building client-side libraries on Ubuntu, 14.04 moves to -9.3.

  [ Christoph Berg ]
  * New upstream security/bug fix release:

    + Fix "VACUUM"'s tests to see whether it can update relfrozenxid
      (Andres Freund)

      In some cases "VACUUM" (either manual or autovacuum) could
      incorrectly advance a table's relfrozenxid value, allowing tuples
      to escape freezing, causing those rows to become invisible once
      2^31 transactions have elapsed. The probability of data loss is
      fairly low since multiple incorrect advancements would need to
      happen before actual loss occurs, but it's not zero. Users
      upgrading from releases 9.0.4 or 8.4.8 or earlier are not affected,
      but all later versions contain the bug.
      The issue can be ameliorated by, after upgrading, vacuuming all
      tables in all databases while having vacuum_freeze_table_age set to
      zero. This will fix any latent corruption but will not be able to
      fix all pre-existing data errors. However, an installation can be
      presumed safe after performing this vacuuming if it has executed
      fewer than 2^31 update transactions in its lifetime (check this
      with SELECT txid_current() < 2^31).

    + Fix initialization of "pg_clog" and "pg_subtrans" during hot
      standby startup (Andres Freund, Heikki Linnakangas)

      This bug can cause data loss on standby servers at the moment they
      start to accept hot-standby queries, by marking committed
      transactions as uncommitted. The likelihood of such corruption is
      small unless, at the time of standby startup, the primary server
      has executed many updating transactions since its last checkpoint.
      Symptoms include missing rows, rows that should have been deleted
      being still visible, and obsolete versions of updated rows being
      still visible alongside their newer versions.
      This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and
      9.0.14. Standby servers that have only been running earlier
      releases are not at risk. It's recommended that standby servers
      that have ever run any of the buggy releases be re-cloned from the
      primary (e.g., with a new base backup) after upgrading.

 -- Christoph Berg <myon@debian.org>  Tue, 03 Dec 2013 09:12:50 +0100

postgresql-9.1 (9.1.10-1) unstable; urgency=low

  * New upstream bug fix release. See changelog.gz for details.
  * Drop 00git-perl5.18.patch, applied upstream.
  * Add 04-config-update.patch: Refresh config.{guess,sub} to latest version
    for enabling ports, in particular arm64 and the upcoming ppc64el.

 -- Martin Pitt <mpitt@debian.org>  Wed, 09 Oct 2013 10:00:31 +0200

postgresql-9.1 (9.1.9-5) unstable; urgency=low

  [ Christoph Berg ]
  * Pull 82b0102650cf85268145a46f0ab488bacf6599a1 from upstream head to better
    support VPATH builds of PGXS modules, and make the install targets depend
    on installdirs.

  [ Martin Pitt ]
  * debian/rules: Still build the client-side libraries on Ubuntu.

 -- Christoph Berg <myon@debian.org>  Tue, 10 Sep 2013 12:24:21 -0400

postgresql-9.1 (9.1.9-4) unstable; urgency=low

  * debian/rules: Ignore test suite failures on hurd (unimplemented
    semaphores) and kfreebsd-* (PL tests known to fail).

 -- Martin Pitt <mpitt@debian.org>  Wed, 28 Aug 2013 10:28:01 +0200

postgresql-9.1 (9.1.9-3) unstable; urgency=low

  [ Martin Pitt ]
  * debian/rules: Support multi-arch locations of {tcl,tk}-config.
  * debian/rules: Don't build with kerberos and LDAP support for
    DEB_STAGE=stage1 to aid with bootstrapping.
  * debian/tests/control: Add missing net-tools dependency (for ifconfig).
  * Add 00git-aarch64.patch: Add ARM64 (aarch64) support to s_lock.h.
    Backported from upstream git.
  * debian/rules: Call dh with --parallel.
  * Add 00git-perl5.18.patch: Adjust PL/Perl test cases to also work for Perl
    5.18. Backported from upstream 9.1 stable branch.
  * debian/rules: Don't build client-side libraries unless we have a pgdg
    version, as these are built by -9.3 now.

  [ Christoph Berg ]
  * Pull 6697aa2bc25c83b88d6165340348a31328c35de6 from upstream head to
    better support VPATH builds of PGXS modules.
  * debian/rules, 60-pg_regress_socketdir: Remove the temporary patches from
    pg_regress, and teach pg_regress to support unix socket dirs in --host.
    Use a random port number as well.
  * debian/rules: Use "make check-world" to run the regression tests. Thanks
    to Peter Eisentraut for the suggestion.
  * 61-extra_regress_opts: Add EXTRA_REGRESS_OPTS in Makefile.global(.in) and
    in src/interfaces/ecpg/test/Makefile.

 -- Martin Pitt <mpitt@debian.org>  Tue, 27 Aug 2013 18:08:50 +0200

postgresql-9.1 (9.1.9-2) unstable; urgency=low

  * debian/copyright: Fix syntax errors.
  * debian/rules: Build with -fno-aggressive-loop-optimizations with gcc 4.8
    to avoid generating bad code due to the broken usage of variable-length
    arrays. This is fixed properly in 9.2, but the patch does not backport
    well. (Closes: #701340)

 -- Martin Pitt <mpitt@debian.org>  Wed, 19 Jun 2013 08:12:14 +0200

postgresql-9.1 (9.1.9-1) unstable; urgency=high

  * Urgency high because of critical remote data destruction vulnerability.
  * New upstream security/bug fix release:
    - Fix insecure parsing of server command-line switches.
      A connection request containing a database name that begins with
      "-" could be crafted to damage or destroy files within the server's
      data directory, even if the request is eventually rejected.
      [CVE-2013-1899] (Closes: #704479)
    - Reset OpenSSL randomness state in each postmaster child process.
      This avoids a scenario wherein random numbers generated by
      "contrib/pgcrypto" functions might be relatively easy for another
      database user to guess. The risk is only significant when the
      postmaster is configured with ssl = on but most connections don't
      use SSL encryption. [CVE-2013-1900]
    - Make REPLICATION privilege checks test current user not
      authenticated user.
      An unprivileged database user could exploit this mistake to call
      pg_start_backup() or pg_stop_backup(), thus possibly interfering
      with creation of routine backups. [CVE-2013-1901]
    - Fix GiST indexes to not use "fuzzy" geometric comparisons when it's
      not appropriate to do so.
      The core geometric types perform comparisons using "fuzzy"
      equality, but gist_box_same must do exact comparisons, else GiST
      indexes using it might become inconsistent. After installing this
      update, users should "REINDEX" any GiST indexes on box, polygon,
      circle, or point columns, since all of these use gist_box_same.
    - Fix erroneous range-union and penalty logic in GiST indexes that
      use "contrib/btree_gist" for variable-width data types, that is
      text, bytea, bit, and numeric columns.
      These errors could result in inconsistent indexes in which some
      keys that are present would not be found by searches, and also in
      useless index bloat. Users are advised to "REINDEX" such indexes
      after installing this update.
    - Fix bugs in GiST page splitting code for multi-column indexes.
      These errors could result in inconsistent indexes in which some
      keys that are present would not be found by searches, and also in
      indexes that are unnecessarily inefficient to search. Users are
      advised to "REINDEX" multi-column GiST indexes after installing
      this update.
    - See HISTORY/changelog.gz for details about the other bug fixes.
  * Bump Standards-Version to 3.9.4 (no changes necessary).

 -- Martin Pitt <mpitt@debian.org>  Tue, 02 Apr 2013 10:26:14 +0200

# For older changelog entries, run 'apt-get changelog postgresql-plperl-9.1'
