Change log for postgresql-9.1 package in Ubuntu

175 of 91 results
Published in trusty-updates on 2016-11-04
Deleted in trusty-proposed (Reason: moved to -updates)
postgresql-9.1 (9.1.24-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Thu, 27 Oct 2016 21:26:48 +0200
Published in precise-updates on 2016-11-04
Deleted in precise-proposed (Reason: moved to -updates)
postgresql-9.1 (9.1.24-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236)
   - Details: https://www.postgresql.org/docs/9.1/static/release-9-1-24.html

 -- Martin Pitt <email address hidden>  Thu, 27 Oct 2016 21:33:45 +0200
Superseded in trusty-updates on 2016-11-04
Published in trusty-security on 2016-08-18
postgresql-9.1 (9.1.23-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream bug fix release (LP: #1614113). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Wed, 17 Aug 2016 16:30:41 +0200
Superseded in precise-updates on 2016-11-04
Published in precise-security on 2016-08-18
postgresql-9.1 (9.1.23-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release (LP: #1614113)
    - Fix possible mis-evaluation of nested CASE-WHEN expressions
      A CASE expression appearing within the test value subexpression of
      another CASE could become confused about whether its own test value was
      null or not.  Also, inlining of a SQL function implementing the equality
      operator used by a CASE expression could result in passing the wrong
      test value to functions called within a CASE expression in the SQL
      function's body.  If the test values were of different data types, a
      crash might result; moreover such situations could be abused to allow
      disclosure of portions of server memory.  (CVE-2016-5423)

    - Fix client programs' handling of special characters in database and role
      names
      Numerous places in vacuumdb and other client programs could become
      confused by database and role names containing double quotes or
      backslashes.  Tighten up quoting rules to make that safe. Also, ensure
      that when a conninfo string is used as a database name parameter to
      these programs, it is correctly treated as such throughout.

      Fix handling of paired double quotes in psql's \connect and \password
      commands to match the documentation.

      Introduce a new -reuse-previous option in psql's \connect command to
      allow explicit control of whether to re-use connection parameters from a
      previous connection.  (Without this, the choice is based on whether the
      database name looks like a conninfo string, as before.)  This allows
      secure handling of database names containing special characters in
      pg_dumpall scripts.

      pg_dumpall now refuses to deal with database and role names containing
      carriage returns or newlines, as it seems impractical to quote those
      characters safely on Windows.  In future we may reject such names on the
      server side, but that step has not been taken yet.

      These are considered security fixes because crafted object names
      containing special characters could have been used to execute commands
      with superuser privileges the next time a superuser executes pg_dumpall
      or other routine maintenance operations.  (CVE-2016-5424)

   - Details: https://www.postgresql.org/docs/9.1/static/release-9-1-23.html

 -- Martin Pitt <email address hidden>  Wed, 17 Aug 2016 16:18:31 +0200
Superseded in trusty-updates on 2016-08-18
Deleted in trusty-proposed on 2016-08-20 (Reason: moved to -updates)
postgresql-9.1 (9.1.22-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1581016). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Thu, 12 May 2016 16:07:46 +0200
Superseded in precise-updates on 2016-08-18
Deleted in precise-proposed on 2016-08-20 (Reason: moved to -updates)
postgresql-9.1 (9.1.22-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release. (LP: #1581016)
    - Details: http://www.postgresql.org/docs/9.1/static/release-9-1-22.html

 -- Martin Pitt <email address hidden>  Thu, 12 May 2016 15:17:22 +0200
Superseded in precise-updates on 2016-05-23
Deleted in precise-proposed on 2016-05-24 (Reason: moved to -updates)
postgresql-9.1 (9.1.21-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream security/bug fix release: (LP: #1564268)
    - See http://www.postgresql.org/about/news/1656/ for details.

 -- Martin Pitt <email address hidden>  Thu, 31 Mar 2016 10:32:50 +0200
Superseded in trusty-updates on 2016-05-23
Deleted in trusty-proposed on 2016-05-24 (Reason: moved to -updates)
postgresql-9.1 (9.1.21-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1564268)
    - In PL/Perl, properly translate empty Postgres arrays into empty Perl
      arrays.

 -- Martin Pitt <email address hidden>  Thu, 31 Mar 2016 11:06:25 +0200
Superseded in precise-updates on 2016-04-07
Superseded in precise-security on 2016-08-18
postgresql-9.1 (9.1.20-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release: (LP: #1544576)
    - Fix infinite loops and buffer-overrun problems in regular expressions.
      Very large character ranges in bracket expressions could cause infinite
      loops in some cases, and memory overwrites in other cases.
      (CVE-2016-0773)
    - Prevent certain PL/Java parameters from being set by non-superusers.
      This change mitigates a PL/Java security bug (CVE-2016-0766), which was
      fixed in PL/Java by marking these parameters as superuser-only. To fix
      the security hazard for sites that update PostgreSQL more frequently
      than PL/Java, make the core code aware of them also.
    - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden>  Thu, 11 Feb 2016 15:41:29 +0100
Superseded in trusty-updates on 2016-04-07
Superseded in trusty-security on 2016-08-18
postgresql-9.1 (9.1.20-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream release (LP: #1544576). No effective changes for PL/Perl, the
    version must just be higher than the one in precise, to not break
    upgrades.

 -- Martin Pitt <email address hidden>  Thu, 11 Feb 2016 15:56:18 +0100
Superseded in trusty-updates on 2016-02-11
Superseded in trusty-security on 2016-02-11
postgresql-9.1 (9.1.19-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream bug fix release (LP: #1504132). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Thu, 08 Oct 2015 15:52:45 +0200
Superseded in precise-updates on 2016-02-11
Superseded in precise-security on 2016-02-11
postgresql-9.1 (9.1.19-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release (LP: #1504132)
    - Fix contrib/pgcrypto to detect and report too-short crypt() salts
      Certain invalid salt arguments crashed the server or disclosed a few
      bytes of server memory.  We have not ruled out the viability of attacks
      that arrange for presence of confidential information in the disclosed
      bytes, but they seem unlikely.  (CVE-2015-5288)
    - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden>  Thu, 08 Oct 2015 16:03:41 +0200
Superseded in precise-updates on 2015-10-16
Deleted in precise-proposed on 2015-10-17 (Reason: moved to -updates)
postgresql-9.1 (9.1.18-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release (LP: #1464669)
    - Fix possible failure to recover from an inconsistent database state
    - Fix rare failure to invalidate relation cache init file
    - See http://www.postgresql.org/about/news/1592/ for details.

 -- Martin Pitt <email address hidden>  Fri, 12 Jun 2015 16:15:01 +0200
Superseded in trusty-updates on 2015-10-16
Deleted in trusty-proposed on 2015-10-17 (Reason: moved to -updates)
postgresql-9.1 (9.1.18-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1464669). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Fri, 12 Jun 2015 16:11:09 +0200
Superseded in precise-updates on 2015-06-24
Deleted in precise-proposed on 2015-06-26 (Reason: moved to -updates)
postgresql-9.1 (9.1.17-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425)
    - Avoid failures while fsync'ing data directory during crash restart.

      In the previous minor releases we added a patch to fsync everything in
      the data directory after a crash.  Unfortunately its response to any
      error condition was to fail, thereby preventing the server from starting
      up, even when the problem was quite harmless.  An example is that an
      unwritable file in the data directory would prevent restart on some
      platforms; but it is common to make SSL certificate files unwritable by
      the server.  Revise this behavior so that permissions failures are
      ignored altogether, and other types of failures are logged but do not
      prevent continuing.

   - See release notes for details about other fixes.

 -- Martin Pitt <email address hidden>  Wed, 03 Jun 2015 09:58:48 +0200
Superseded in trusty-updates on 2015-06-24
Deleted in trusty-proposed on 2015-06-26 (Reason: moved to -updates)
postgresql-9.1 (9.1.17-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1461425). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.

 -- Martin Pitt <email address hidden>  Wed, 03 Jun 2015 09:56:12 +0200
Superseded in precise-updates on 2015-06-09
Superseded in precise-security on 2015-10-16
postgresql-9.1 (9.1.16-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release (LP: #1457093)
    - Avoid possible crash when client disconnects just before the
      authentication timeout expires.
      If the timeout interrupt fired partway through the session shutdown
      sequence, SSL-related state would be freed twice, typically causing a
      crash and hence denial of service to other sessions.  Experimentation
      shows that an unauthenticated remote attacker could trigger the bug
      somewhat consistently, hence treat as security issue. (CVE-2015-3165)

    - Improve detection of system-call failures
      Our replacement implementation of snprintf() failed to check for errors
      reported by the underlying system library calls; the main case that
      might be missed is out-of-memory situations. In the worst case this
      might lead to information exposure, due to our code assuming that a
      buffer had been overwritten when it hadn't been. Also, there were a few
      places in which security-relevant calls of other system library
      functions did not check for failure.
      It remains possible that some calls of the *printf() family of functions
      are vulnerable to information disclosure if an out-of-memory error
      occurs at just the wrong time.  We judge the risk to not be large, but
      will continue analysis in this area. (CVE-2015-3166)

    - In contrib/pgcrypto, uniformly report decryption failures as Wrong key
      or corrupt data
      Previously, some cases of decryption with an incorrect key could report
      other error message texts.  It has been shown that such variance in
      error reports can aid attackers in recovering keys from other systems.
      While it's unknown whether pgcrypto's specific behaviors are likewise
      exploitable, it seems better to avoid the risk by using a
      one-size-fits-all message. (CVE-2015-3167)

    - Protect against wraparound of multixact member IDs
      Under certain usage patterns, the existing defenses against this might
      be insufficient, allowing pg_multixact/members files to be removed too
      early, resulting in data loss.
      The fix for this includes modifying the server to fail transactions that
      would result in overwriting old multixact member ID data, and improving
      autovacuum to ensure it will act proactively to prevent multixact member
      ID wraparound, as it does for transaction ID wraparound.

   - See release notes for details about other fixes.

  * Backport the autopkgtest, as running the postgresql-common integration
    test suite is a lot simpler that way. Add manual creation of required
    locales, as precise's postgresql-common test suite does not yet do that by
    itself.

 -- Martin Pitt <email address hidden>  Wed, 20 May 2015 23:25:56 +0200
Superseded in trusty-updates on 2015-06-09
Superseded in trusty-security on 2015-10-16
postgresql-9.1 (9.1.16-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream security/bug fix release (LP: #1457093)
    - Improve detection of system-call failures
      Our replacement implementation of snprintf() failed to check for errors
      reported by the underlying system library calls; the main case that
      might be missed is out-of-memory situations. In the worst case this
      might lead to information exposure, due to our code assuming that a
      buffer had been overwritten when it hadn't been. Also, there were a few
      places in which security-relevant calls of other system library
      functions did not check for failure.
      It remains possible that some calls of the *printf() family of functions
      are vulnerable to information disclosure if an out-of-memory error
      occurs at just the wrong time.  We judge the risk to not be large, but
      will continue analysis in this area. (CVE-2015-3166)
   - Note: The other vulnerabilities fixed in 9.1.16 don't affect this version
     as we build the PL/Perl package only.

 -- Martin Pitt <email address hidden>  Wed, 20 May 2015 23:16:18 +0200
Superseded in precise-updates on 2015-05-25
Superseded in precise-security on 2015-05-25
postgresql-9.1 (9.1.15-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bug fix release (LP: #1418928)
    - Fix buffer overruns in to_char() [CVE-2015-0241]
    - Fix buffer overruns in contrib/pgcrypto [CVE-2015-0243]
    - Fix possible loss of frontend/backend protocol synchronization after an
      error [CVE-2015-0244]
    - Fix information leak via constraint-violation error messages
      [CVE-2014-8161]
    - See release notes for details about other fixes:
      http://www.postgresql.org/about/news/1569/
 -- Martin Pitt <email address hidden>   Fri, 06 Feb 2015 12:58:26 +0100
Superseded in trusty-updates on 2015-05-25
Superseded in trusty-security on 2015-05-25
postgresql-9.1 (9.1.15-0ubuntu0.14.04) trusty-security; urgency=medium

  * New upstream bug fix release (LP: #1418928). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.
 -- Martin Pitt <email address hidden>   Fri, 06 Feb 2015 12:53:38 +0100
Superseded in trusty-updates on 2015-02-11
Deleted in trusty-proposed on 2015-02-13 (Reason: moved to -updates)
postgresql-9.1 (9.1.14-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1348176). No effective changes for
    PL/Perl, the version must just be higher than the one in precise, to not
    break upgrades.
  * Drop pg_regress patches to run tests with socket in /tmp, obsolete with
    upstream changes and not applicable any more.
 -- Martin Pitt <email address hidden>   Tue, 29 Jul 2014 14:58:28 +0200
Superseded in precise-updates on 2015-02-11
Deleted in precise-proposed on 2015-02-13 (Reason: moved to -updates)
postgresql-9.1 (9.1.14-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release: (LP: #1348176)
    - Various data integrity and other bug fixes.
    - Secure Unix-domain sockets of temporary postmasters started during make
       check.
       Any local user able to access the socket file could connect as the
       server's bootstrap superuser, then proceed to execute arbitrary code as
       the operating-system user running the test, as we previously noted in
       CVE-2014-0067. This change defends against that risk by placing the
       server's socket in a temporary, mode 0700 subdirectory of /tmp.
    - See release notes for details:
      http://www.postgresql.org/docs/current/static/release-9-1-14.html
  * Drop pg_regress patches to run tests with socket in /tmp, obsolete with
    above upstream changes and not applicable any more.
 -- Martin Pitt <email address hidden>   Thu, 24 Jul 2014 18:09:12 +0200
Deleted in utopic-release (Reason: superseded by postgresql-9.3, was only for upgrades to tr...)
Published in trusty-release on 2014-03-21
Deleted in trusty-proposed (Reason: moved to release)
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 <email address hidden>  Tue, 18 Mar 2014 10:18:13 +0100

Available diffs

Superseded in precise-updates on 2014-08-06
Deleted in precise-proposed on 2014-08-08 (Reason: moved to -updates)
postgresql-9.1 (9.1.13-0ubuntu0.12.04) precise-proposed; urgency=medium

  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)
 -- Martin Pitt <email address hidden>   Tue, 18 Mar 2014 10:41:28 +0100
Obsolete in quantal-updates on 2015-04-24
Deleted in quantal-proposed on 2015-05-01 (Reason: moved to -updates)
postgresql-9.1 (9.1.13-0ubuntu0.12.10) quantal-proposed; urgency=medium

  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)
 -- Martin Pitt <email address hidden>   Tue, 18 Mar 2014 10:31:14 +0100
Obsolete in saucy-updates on 2015-04-24
Deleted in saucy-proposed on 2015-04-28 (Reason: moved to -updates)
postgresql-9.1 (9.1.13-0ubuntu0.13.10) saucy-proposed; urgency=medium

  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)
 -- Martin Pitt <email address hidden>   Tue, 18 Mar 2014 10:26:43 +0100
Superseded in saucy-updates on 2014-03-31
Obsolete in saucy-security on 2015-04-24
postgresql-9.1 (9.1.12-0ubuntu0.13.10) saucy-security; urgency=medium

  * New upstream security/bugfix release. (LP: #1282677)
    - Shore up GRANT ... WITH ADMIN OPTION restrictions.
      Granting a role without ADMIN OPTION is supposed to prevent the grantee
      from adding or removing members from the granted role, but this
      restriction was easily bypassed by doing SET ROLE first. The security
      impact is mostly that a role member can revoke the access of others,
      contrary to the wishes of his grantor. Unapproved role member additions
      are a lesser concern, since an uncooperative role member could provide
      most of his rights to others anyway by creating views or SECURITY
      DEFINER functions. (CVE-2014-0060)
    - Prevent privilege escalation via manual calls to PL validator functions.
      The primary role of PL validator functions is to be called implicitly
      during CREATE FUNCTION, but they are also normal SQL functions that a
      user can call explicitly. Calling a validator on a function actually
      written in some other language was not checked for and could be
      exploited for privilege-escalation purposes. The fix involves adding a
      call to a privilege-checking function in each validator function.
      Non-core procedural languages will also need to make this change to
      their own validator functions, if any. (CVE-2014-0061)
    - Avoid multiple name lookups during table and index DDL.
      If the name lookups come to different conclusions due to concurrent
      activity, we might perform some parts of the DDL on a different table
      than other parts. At least in the case of CREATE INDEX, this can be used
      to cause the permissions checks to be performed against a different
      table than the index creation, allowing for a privilege escalation
      attack. (CVE-2014-0062)
    - Prevent buffer overrun with long datetime strings.
      The MAXDATELEN constant was too small for the longest possible value of
      type interval, allowing a buffer overrun in interval_out(). Although the
      datetime input functions were more careful about avoiding buffer
      overrun, the limit was short enough to cause them to reject some valid
      inputs, such as input containing a very long timezone name. The ecpg
      library contained these vulnerabilities along with some of its own.
      (CVE-2014-0063)
    - Prevent buffer overrun due to integer overflow in size calculations.
      Several functions, mostly type input functions, calculated an allocation
      size without checking for overflow. If overflow did occur, a too-small
      buffer would be allocated and then written past. (CVE-2014-0064)
    - Prevent overruns of fixed-size buffers.
      Use strlcpy() and related functions to provide a clear guarantee that
      fixed-size buffers are not overrun. Unlike the preceding items, it is
      unclear whether these cases really represent live issues, since in most
      cases there appear to be previous constraints on the size of the input
      string. Nonetheless it seems prudent to silence all Coverity warnings of
      this type. (CVE-2014-0065)
    - Avoid crashing if crypt() returns NULL.
      There are relatively few scenarios in which crypt() could return NULL,
      but contrib/chkpass would crash if it did. One practical case in which
      this could be an issue is if libc is configured to refuse to execute
      unapproved hashing algorithms (e.g., "FIPS mode"). (CVE-2014-0066)
    - Document risks of make check in the regression testing instructions
      Since the temporary server started by make check uses "trust"
      authentication, another user on the same machine could connect to it as
      database superuser, and then potentially exploit the privileges of the
      operating-system user who started the tests. A future release will
      probably incorporate changes in the testing procedure to prevent this
      risk, but some public discussion is needed first. So for the moment,
      just warn people against using make check when there are untrusted users
      on the same machine. (CVE-2014-0067)
  * The upstream tarballs no longer contain a plain HISTORY file, but point to
    the html documentation. Add 70-history.patch to note the location of these
    files in our changelog.gz file.
 -- Martin Pitt <email address hidden>   Thu, 20 Feb 2014 08:49:25 -0800
Superseded in quantal-updates on 2014-03-31
Obsolete in quantal-security on 2015-04-24
postgresql-9.1 (9.1.12-0ubuntu0.12.10) quantal-security; urgency=medium

  * New upstream security/bugfix release. (LP: #1282677)
    - Shore up GRANT ... WITH ADMIN OPTION restrictions.
      Granting a role without ADMIN OPTION is supposed to prevent the grantee
      from adding or removing members from the granted role, but this
      restriction was easily bypassed by doing SET ROLE first. The security
      impact is mostly that a role member can revoke the access of others,
      contrary to the wishes of his grantor. Unapproved role member additions
      are a lesser concern, since an uncooperative role member could provide
      most of his rights to others anyway by creating views or SECURITY
      DEFINER functions. (CVE-2014-0060)
    - Prevent privilege escalation via manual calls to PL validator functions.
      The primary role of PL validator functions is to be called implicitly
      during CREATE FUNCTION, but they are also normal SQL functions that a
      user can call explicitly. Calling a validator on a function actually
      written in some other language was not checked for and could be
      exploited for privilege-escalation purposes. The fix involves adding a
      call to a privilege-checking function in each validator function.
      Non-core procedural languages will also need to make this change to
      their own validator functions, if any. (CVE-2014-0061)
    - Avoid multiple name lookups during table and index DDL.
      If the name lookups come to different conclusions due to concurrent
      activity, we might perform some parts of the DDL on a different table
      than other parts. At least in the case of CREATE INDEX, this can be used
      to cause the permissions checks to be performed against a different
      table than the index creation, allowing for a privilege escalation
      attack. (CVE-2014-0062)
    - Prevent buffer overrun with long datetime strings.
      The MAXDATELEN constant was too small for the longest possible value of
      type interval, allowing a buffer overrun in interval_out(). Although the
      datetime input functions were more careful about avoiding buffer
      overrun, the limit was short enough to cause them to reject some valid
      inputs, such as input containing a very long timezone name. The ecpg
      library contained these vulnerabilities along with some of its own.
      (CVE-2014-0063)
    - Prevent buffer overrun due to integer overflow in size calculations.
      Several functions, mostly type input functions, calculated an allocation
      size without checking for overflow. If overflow did occur, a too-small
      buffer would be allocated and then written past. (CVE-2014-0064)
    - Prevent overruns of fixed-size buffers.
      Use strlcpy() and related functions to provide a clear guarantee that
      fixed-size buffers are not overrun. Unlike the preceding items, it is
      unclear whether these cases really represent live issues, since in most
      cases there appear to be previous constraints on the size of the input
      string. Nonetheless it seems prudent to silence all Coverity warnings of
      this type. (CVE-2014-0065)
    - Avoid crashing if crypt() returns NULL.
      There are relatively few scenarios in which crypt() could return NULL,
      but contrib/chkpass would crash if it did. One practical case in which
      this could be an issue is if libc is configured to refuse to execute
      unapproved hashing algorithms (e.g., "FIPS mode"). (CVE-2014-0066)
    - Document risks of make check in the regression testing instructions
      Since the temporary server started by make check uses "trust"
      authentication, another user on the same machine could connect to it as
      database superuser, and then potentially exploit the privileges of the
      operating-system user who started the tests. A future release will
      probably incorporate changes in the testing procedure to prevent this
      risk, but some public discussion is needed first. So for the moment,
      just warn people against using make check when there are untrusted users
      on the same machine. (CVE-2014-0067)
  * The upstream tarballs no longer contain a plain HISTORY file, but point to
    the html documentation. Add 70-history.patch to note the location of these
    files in our changelog.gz file.
 -- Martin Pitt <email address hidden>   Thu, 20 Feb 2014 09:51:51 -0800
Superseded in precise-updates on 2014-03-31
Superseded in precise-security on 2015-02-11
postgresql-9.1 (9.1.12-0ubuntu0.12.04) precise-security; urgency=medium

  * New upstream security/bugfix release. (LP: #1282677)
    - Shore up GRANT ... WITH ADMIN OPTION restrictions.
      Granting a role without ADMIN OPTION is supposed to prevent the grantee
      from adding or removing members from the granted role, but this
      restriction was easily bypassed by doing SET ROLE first. The security
      impact is mostly that a role member can revoke the access of others,
      contrary to the wishes of his grantor. Unapproved role member additions
      are a lesser concern, since an uncooperative role member could provide
      most of his rights to others anyway by creating views or SECURITY
      DEFINER functions. (CVE-2014-0060)
    - Prevent privilege escalation via manual calls to PL validator functions.
      The primary role of PL validator functions is to be called implicitly
      during CREATE FUNCTION, but they are also normal SQL functions that a
      user can call explicitly. Calling a validator on a function actually
      written in some other language was not checked for and could be
      exploited for privilege-escalation purposes. The fix involves adding a
      call to a privilege-checking function in each validator function.
      Non-core procedural languages will also need to make this change to
      their own validator functions, if any. (CVE-2014-0061)
    - Avoid multiple name lookups during table and index DDL.
      If the name lookups come to different conclusions due to concurrent
      activity, we might perform some parts of the DDL on a different table
      than other parts. At least in the case of CREATE INDEX, this can be used
      to cause the permissions checks to be performed against a different
      table than the index creation, allowing for a privilege escalation
      attack. (CVE-2014-0062)
    - Prevent buffer overrun with long datetime strings.
      The MAXDATELEN constant was too small for the longest possible value of
      type interval, allowing a buffer overrun in interval_out(). Although the
      datetime input functions were more careful about avoiding buffer
      overrun, the limit was short enough to cause them to reject some valid
      inputs, such as input containing a very long timezone name. The ecpg
      library contained these vulnerabilities along with some of its own.
      (CVE-2014-0063)
    - Prevent buffer overrun due to integer overflow in size calculations.
      Several functions, mostly type input functions, calculated an allocation
      size without checking for overflow. If overflow did occur, a too-small
      buffer would be allocated and then written past. (CVE-2014-0064)
    - Prevent overruns of fixed-size buffers.
      Use strlcpy() and related functions to provide a clear guarantee that
      fixed-size buffers are not overrun. Unlike the preceding items, it is
      unclear whether these cases really represent live issues, since in most
      cases there appear to be previous constraints on the size of the input
      string. Nonetheless it seems prudent to silence all Coverity warnings of
      this type. (CVE-2014-0065)
    - Avoid crashing if crypt() returns NULL.
      There are relatively few scenarios in which crypt() could return NULL,
      but contrib/chkpass would crash if it did. One practical case in which
      this could be an issue is if libc is configured to refuse to execute
      unapproved hashing algorithms (e.g., "FIPS mode"). (CVE-2014-0066)
    - Document risks of make check in the regression testing instructions
      Since the temporary server started by make check uses "trust"
      authentication, another user on the same machine could connect to it as
      database superuser, and then potentially exploit the privileges of the
      operating-system user who started the tests. A future release will
      probably incorporate changes in the testing procedure to prevent this
      risk, but some public discussion is needed first. So for the moment,
      just warn people against using make check when there are untrusted users
      on the same machine. (CVE-2014-0067)
  * The upstream tarballs no longer contain a plain HISTORY file, but point to
    the html documentation. Add 70-history.patch to note the location of these
    files in our changelog.gz file.
 -- Martin Pitt <email address hidden>   Thu, 20 Feb 2014 11:35:10 -0800
Superseded in trusty-release on 2014-03-21
Deleted in trusty-proposed on 2014-03-22 (Reason: moved to release)
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 <email address hidden>  Thu, 20 Feb 2014 08:02:45 -0800

Available diffs

Superseded in trusty-release on 2014-02-21
Deleted in trusty-proposed on 2014-02-22 (Reason: moved to release)
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 <email address hidden>  Tue, 17 Dec 2013 11:19:04 +0100

Available diffs

Superseded in trusty-release on 2014-01-08
Superseded in trusty-release on 2013-12-21
Deleted in trusty-proposed on 2014-01-22 (Reason: moved to release)
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 <email address hidden>  Tue, 03 Dec 2013 09:12:50 +0100
Superseded in precise-updates on 2014-02-24
Deleted in precise-proposed on 2014-02-25 (Reason: moved to -updates)
postgresql-9.1 (9.1.11-0ubuntu0.12.04) precise-proposed; urgency=low

  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      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.
      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.
    - See HISTORY/changelog.gz for details about other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 03 Dec 2013 10:37:18 +0100
Superseded in quantal-updates on 2014-02-24
Deleted in quantal-proposed on 2014-02-25 (Reason: moved to -updates)
postgresql-9.1 (9.1.11-0ubuntu0.12.10) quantal-proposed; urgency=low

  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      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.
      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.
    - See HISTORY/changelog.gz for details about other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 03 Dec 2013 10:30:25 +0100
Obsolete in raring-updates on 2015-04-24
Deleted in raring-proposed on 2015-04-27 (Reason: moved to -updates)
postgresql-9.1 (9.1.11-0ubuntu0.13.04) raring-proposed; urgency=low

  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      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.
      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.
    - See HISTORY/changelog.gz for details about other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 03 Dec 2013 10:22:12 +0100
Superseded in saucy-updates on 2014-02-24
Deleted in saucy-proposed on 2014-02-25 (Reason: moved to -updates)
postgresql-9.1 (9.1.11-0ubuntu0.13.10) saucy-proposed; urgency=low

  * New upstream bug fix release. (LP: #1257211)
    - Fix "VACUUM"'s tests to see whether it can update relfrozenxid.
      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.
      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.
    - See HISTORY/changelog.gz for details about other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 03 Dec 2013 10:16:56 +0100
Superseded in trusty-release on 2013-12-06
Deleted in trusty-proposed on 2013-12-07 (Reason: moved to release)
postgresql-9.1 (9.1.10-1bzr1) trusty; urgency=low

  * Upload current Debian packaging trunk to rebuild against Perl 5.18.
  * Stop building client-side libraries on Ubuntu, 14.04 moves to -9.3.
 -- Martin Pitt <email address hidden>   Mon, 21 Oct 2013 22:06:20 +0200
Superseded in trusty-release on 2013-10-24
Obsolete in saucy-release on 2015-04-24
Deleted in saucy-proposed on 2015-04-28 (Reason: moved to release)
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 <email address hidden>  Wed, 09 Oct 2013 10:00:31 +0200

Available diffs

Superseded in precise-updates on 2013-12-10
Deleted in precise-proposed on 2013-12-11 (Reason: moved to -updates)
postgresql-9.1 (9.1.10-0ubuntu12.04) precise-proposed; urgency=low

  * New upstream bug fix release (LP: #1237248). No security issues or
    critical issues this time; see HISTORY/changelog.gz for details about bug
    fixes.
 -- Martin Pitt <email address hidden>   Wed, 09 Oct 2013 10:05:58 +0200
Superseded in quantal-updates on 2013-12-10
Deleted in quantal-proposed on 2013-12-11 (Reason: moved to -updates)
postgresql-9.1 (9.1.10-0ubuntu12.10) quantal-proposed; urgency=low

  * New upstream bug fix release (LP: #1237248). No security issues or
    critical issues this time; see HISTORY/changelog.gz for details about bug
    fixes.
 -- Martin Pitt <email address hidden>   Wed, 09 Oct 2013 09:56:28 +0200
Superseded in raring-updates on 2013-12-10
Deleted in raring-proposed on 2013-12-11 (Reason: moved to -updates)
postgresql-9.1 (9.1.10-0ubuntu13.04) raring-proposed; urgency=low

  * New upstream bug fix release (LP: #1237248). No security issues or
    critical issues this time; see HISTORY/changelog.gz for details about bug
    fixes.
 -- Martin Pitt <email address hidden>   Wed, 09 Oct 2013 09:34:32 +0200
Superseded in saucy-release on 2013-10-11
Deleted in saucy-proposed on 2013-10-12 (Reason: moved to release)
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 <email address hidden>  Tue, 10 Sep 2013 12:24:21 -0400
Superseded in saucy-proposed on 2013-09-11
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 <email address hidden>  Tue, 27 Aug 2013 18:08:50 +0200
Superseded in saucy-release on 2013-09-11
Deleted in saucy-proposed on 2013-09-12 (Reason: moved to release)
postgresql-9.1 (9.1.9-2bzr1) saucy; urgency=low

  Upload current Debian packaging bzr head (which generalized and applied the
  recent Ubuntu delta) and fix FTBFS with gcc-4.8.

  * debian/rules: Support multi-arch locations of {tcl,tk}-config.

Available diffs

Superseded in saucy-release on 2013-07-05
Obsolete in raring-release on 2015-04-24
Deleted in raring-proposed on 2015-04-27 (Reason: moved to release)
postgresql-9.1 (9.1.9-1ubuntu1) raring; urgency=low

  * Merge with Debian unstable. (LP: #1163184) Remaining Ubuntu changes:
    - debian/rules: Configure for the Tcl/Tk 8.5 multiarch installation.

Available diffs

Superseded in quantal-updates on 2013-10-24
Superseded in quantal-security on 2014-02-24
postgresql-9.1 (9.1.9-0ubuntu12.10) quantal-security; urgency=low

  * New upstream security/bug fix release: (LP: #1163184)
    - 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]
    - 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.
 -- Martin Pitt <email address hidden>   Tue, 02 Apr 2013 11:52:28 +0200
Superseded in precise-updates on 2013-10-24
Superseded in precise-security on 2014-02-24
postgresql-9.1 (9.1.9-0ubuntu12.04) precise-security; urgency=low

  * New upstream security/bug fix release: (LP: #1163184)
    - 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]
    - 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.
 -- Martin Pitt <email address hidden>   Tue, 02 Apr 2013 11:59:41 +0200
Obsolete in oneiric-updates on 2015-04-24
Obsolete in oneiric-security on 2015-04-24
postgresql-9.1 (9.1.9-0ubuntu11.10) oneiric-security; urgency=low

  * New upstream security/bug fix release: (LP: #1163184)
    - 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]
    - 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.
 -- Martin Pitt <email address hidden>   Tue, 02 Apr 2013 12:24:32 +0200
Superseded in raring-release on 2013-04-04
Deleted in raring-proposed on 2013-04-05 (Reason: moved to release)
postgresql-9.1 (9.1.8-1ubuntu1) raring; urgency=low

  * Configure for the Tcl/Tk 8.5 multiarch installation.
 -- Matthias Klose <email address hidden>   Tue, 02 Apr 2013 11:03:40 +0200
Superseded in oneiric-updates on 2013-04-04
Superseded in oneiric-security on 2013-04-04
postgresql-9.1 (9.1.8-0ubuntu11.10) oneiric-security; urgency=low

  * New upstream security/bug fix release: (LP: #1116336)
    - Prevent execution of enum_recv from SQL
      The function was misdeclared, allowing a simple SQL command to crash the
      server.  In principle an attacker might be able to use it to examine the
      contents of server memory.  Our thanks to Sumit Soni (via Secunia SVCRP)
      for reporting this issue. (CVE-2013-0255)
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 05 Feb 2013 18:13:52 +0100
Superseded in quantal-updates on 2013-04-04
Superseded in quantal-security on 2013-04-04
postgresql-9.1 (9.1.8-0ubuntu12.10) quantal-security; urgency=low

  * New upstream security/bug fix release: (LP: #1116336)
    - Prevent execution of enum_recv from SQL
      The function was misdeclared, allowing a simple SQL command to crash the
      server.  In principle an attacker might be able to use it to examine the
      contents of server memory.  Our thanks to Sumit Soni (via Secunia SVCRP)
      for reporting this issue. (CVE-2013-0255)
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 05 Feb 2013 16:07:05 +0100
Superseded in raring-release on 2013-04-02
Deleted in raring-proposed on 2013-04-03 (Reason: moved to release)
postgresql-9.1 (9.1.8-1) unstable; urgency=medium


  [ Martin Pitt ]
  * Add autopkgtest, moved from postgresql-common.
  * debian/rules: Only build the error codes and the plpython subtree for the
    "python3" flavor, to cut down build time.
  * Add missing docbook build dependency. (Closes: #697618)

  [ Christoph Berg ]
  * New upstream version.
    + Prevent execution of enum_recv from SQL
      The function was misdeclared, allowing a simple SQL command to crash the
      server.  In principle an attacker might be able to use it to examine the
      contents of server memory.  Our thanks to Sumit Soni (via Secunia SVCRP)
      for reporting this issue. (CVE-2013-0255)

 -- Christoph Berg <email address hidden>  Tue, 05 Feb 2013 14:15:33 +0100
Superseded in precise-updates on 2013-04-04
Superseded in precise-security on 2013-04-04
postgresql-9.1 (9.1.8-0ubuntu12.04) precise-security; urgency=low

  * New upstream security/bug fix release: (LP: #1116336)
    - Prevent execution of enum_recv from SQL
      The function was misdeclared, allowing a simple SQL command to crash the
      server.  In principle an attacker might be able to use it to examine the
      contents of server memory.  Our thanks to Sumit Soni (via Secunia SVCRP)
      for reporting this issue. (CVE-2013-0255)
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 05 Feb 2013 16:19:31 +0100
Superseded in raring-release on 2013-02-07
Deleted in raring-proposed on 2013-02-09 (Reason: moved to release)
postgresql-9.1 (9.1.7-1bzr1) raring; urgency=low

  * Add autopkgtest, moved from postgresql-common.
  * debian/rules: Only build the error codes and the plpython subtree for the
    "python3" flavor, to cut down build time.
 -- Martin Pitt <email address hidden>   Mon, 07 Jan 2013 08:30:03 +0100

Available diffs

Superseded in precise-updates on 2013-02-14
Deleted in precise-proposed on 2013-02-16 (Reason: moved to -updates)
postgresql-9.1 (9.1.7-0ubuntu12.04) precise-proposed; urgency=low

  * New upstream bug fix release: (LP: #1088393)
    - Fix multiple bugs associated with "CREATE INDEX CONCURRENTLY".
      Fix "CREATE INDEX CONCURRENTLY" to use in-place updates when
      changing the state of an index's pg_index row. This prevents race
      conditions that could cause concurrent sessions to miss updating
      the target index, thus resulting in corrupt concurrently-created
      indexes.
      Also, fix various other operations to ensure that they ignore
      invalid indexes resulting from a failed "CREATE INDEX CONCURRENTLY"
      command. The most important of these is "VACUUM", because an
      auto-vacuum could easily be launched on the table before corrective
      action can be taken to fix or remove the invalid index.
    - Fix buffer locking during WAL replay.
      The WAL replay code was insufficiently careful about locking
      buffers when replaying WAL records that affect more than one page.
      This could result in hot standby queries transiently seeing
      inconsistent states, resulting in wrong answers or unexpected
      failures.
    - See HISTORY/changelog.gz for the other bug fixes.
  * Drop 00git_ecpg_array_bounds.patch, fixed upstream.
 -- Martin Pitt <email address hidden>   Mon, 10 Dec 2012 14:54:49 +0100
Superseded in quantal-updates on 2013-02-14
Deleted in quantal-proposed on 2013-02-16 (Reason: moved to -updates)
postgresql-9.1 (9.1.7-0ubuntu12.10) quantal-proposed; urgency=low

  * New upstream bug fix release: (LP: #1088393)
    - Fix multiple bugs associated with "CREATE INDEX CONCURRENTLY".
      Fix "CREATE INDEX CONCURRENTLY" to use in-place updates when
      changing the state of an index's pg_index row. This prevents race
      conditions that could cause concurrent sessions to miss updating
      the target index, thus resulting in corrupt concurrently-created
      indexes.
      Also, fix various other operations to ensure that they ignore
      invalid indexes resulting from a failed "CREATE INDEX CONCURRENTLY"
      command. The most important of these is "VACUUM", because an
      auto-vacuum could easily be launched on the table before corrective
      action can be taken to fix or remove the invalid index.
    - Fix buffer locking during WAL replay.
      The WAL replay code was insufficiently careful about locking
      buffers when replaying WAL records that affect more than one page.
      This could result in hot standby queries transiently seeing
      inconsistent states, resulting in wrong answers or unexpected
      failures.
    - See HISTORY/changelog.gz for the other bug fixes.
  * Drop 00git_ecpg_array_bounds.patch, fixed upstream.
 -- Martin Pitt <email address hidden>   Mon, 10 Dec 2012 15:00:57 +0100
Superseded in oneiric-updates on 2013-02-14
Deleted in oneiric-proposed on 2013-02-16 (Reason: moved to -updates)
postgresql-9.1 (9.1.7-0ubuntu11.10) oneiric-proposed; urgency=low

  * New upstream bug fix release: (LP: #1088393)
    - Fix multiple bugs associated with "CREATE INDEX CONCURRENTLY".
      Fix "CREATE INDEX CONCURRENTLY" to use in-place updates when
      changing the state of an index's pg_index row. This prevents race
      conditions that could cause concurrent sessions to miss updating
      the target index, thus resulting in corrupt concurrently-created
      indexes.
      Also, fix various other operations to ensure that they ignore
      invalid indexes resulting from a failed "CREATE INDEX CONCURRENTLY"
      command. The most important of these is "VACUUM", because an
      auto-vacuum could easily be launched on the table before corrective
      action can be taken to fix or remove the invalid index.
    - Fix buffer locking during WAL replay.
      The WAL replay code was insufficiently careful about locking
      buffers when replaying WAL records that affect more than one page.
      This could result in hot standby queries transiently seeing
      inconsistent states, resulting in wrong answers or unexpected
      failures.
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Mon, 10 Dec 2012 15:04:42 +0100
Superseded in raring-release on 2013-01-07
Deleted in raring-proposed on 2013-01-08 (Reason: moved to release)
postgresql-9.1 (9.1.7-1) unstable; urgency=low


  * New upstream bug fix release. See HISTORY/changelog.gz for details.
  * Add 03-python-includedirs.patch: Detect both python3.3 include locations.
    Thanks Dmitrijs Ledkovs!

 -- Martin Pitt <email address hidden>  Mon, 03 Dec 2012 22:32:35 +0000
Superseded in raring-release on 2012-12-10
Deleted in raring-proposed on 2012-12-11 (Reason: moved to release)
postgresql-9.1 (9.1.6-1ubuntu2) raring; urgency=low

  * Add patch for python3.3 support
  * Rebuild against python3.3.

Superseded in precise-updates on 2012-12-19
Deleted in precise-proposed on 2012-12-20 (Reason: moved to -updates)
postgresql-9.1 (9.1.6-0ubuntu12.04.1) precise-proposed; urgency=low

  * Add debian/patches/00git_ecpg_array_bounds.patch: Fix test for array
    boundary in ecpg. Patch backported from upstream git. (LP: #1063613)
 -- Martin Pitt <email address hidden>   Thu, 18 Oct 2012 17:36:30 +0200
Superseded in quantal-updates on 2012-12-19
Deleted in quantal-proposed on 2012-12-20 (Reason: moved to -updates)
postgresql-9.1 (9.1.6-1ubuntu1) quantal-proposed; urgency=low

  * Add debian/patches/00git_ecpg_array_bounds.patch: Fix test for array
    boundary in ecpg. Patch backported from upstream git. (LP: #1063613)
 -- Martin Pitt <email address hidden>   Thu, 18 Oct 2012 17:31:07 +0200
Superseded in raring-release on 2012-10-31
Obsolete in quantal-release on 2015-04-24
postgresql-9.1 (9.1.6-1) unstable; urgency=medium


  * Urgency medium because of data loss bug fix.
  * New upstream bug fix release:
    - Fix persistence marking of shared buffers during WAL replay.
      This mistake can result in buffers not being written out during
      checkpoints, resulting in data corruption if the server later
      crashes without ever having written those buffers. Corruption can
      occur on any server following crash recovery, but it is
      significantly more likely to occur on standby slave servers since
      those perform much more WAL replay. There is a low probability of
      corruption of btree and GIN indexes. There is a much higher
      probability of corruption of table "visibility maps". Fortunately,
      visibility maps are non-critical data in 9.1, so the worst
      consequence of such corruption in 9.1 installations is transient
      inefficiency of vacuuming. Table data proper cannot be corrupted by
      this bug.
      While no index corruption due to this bug is known to have occurred
      in the field, as a precautionary measure it is recommended that
      production installations "REINDEX" all btree and GIN indexes at a
      convenient time after upgrading to 9.1.6.
      Also, if you intend to do an in-place upgrade to 9.2.X, before
      doing so it is recommended to perform a "VACUUM" of all tables
      while having vacuum_freeze_table_age set to zero. This will ensure
      that any lingering wrong data in the visibility maps is corrected
      before 9.2.X can depend on it. vacuum_cost_delay can be adjusted to
      reduce the performance impact of vacuuming, while causing it to
      take longer to finish.
    - See HISTORY/changelog.gz for the other bug fixes.
  * debian/rules: Compress all binaries with xz. Thanks Cyril Brulebois!
    (Closes: #688678)

 -- Martin Pitt <email address hidden>  Tue, 25 Sep 2012 05:40:23 +0200

Available diffs

Superseded in oneiric-updates on 2012-12-19
Deleted in oneiric-proposed on 2012-12-20 (Reason: moved to -updates)
postgresql-9.1 (9.1.6-0ubuntu11.10) oneiric-proposed; urgency=low

  * New upstream bug fix release: (LP: #1055944)
    - Fix persistence marking of shared buffers during WAL replay.
      This mistake can result in buffers not being written out during
      checkpoints, resulting in data corruption if the server later
      crashes without ever having written those buffers. Corruption can
      occur on any server following crash recovery, but it is
      significantly more likely to occur on standby slave servers since
      those perform much more WAL replay. There is a low probability of
      corruption of btree and GIN indexes. There is a much higher
      probability of corruption of table "visibility maps". Fortunately,
      visibility maps are non-critical data in 9.1, so the worst
      consequence of such corruption in 9.1 installations is transient
      inefficiency of vacuuming. Table data proper cannot be corrupted by
      this bug.
      While no index corruption due to this bug is known to have occurred
      in the field, as a precautionary measure it is recommended that
      production installations "REINDEX" all btree and GIN indexes at a
      convenient time after upgrading to 9.1.6.
      Also, if you intend to do an in-place upgrade to 9.2.X, before
      doing so it is recommended to perform a "VACUUM" of all tables
      while having vacuum_freeze_table_age set to zero. This will ensure
      that any lingering wrong data in the visibility maps is corrected
      before 9.2.X can depend on it. vacuum_cost_delay can be adjusted to
      reduce the performance impact of vacuuming, while causing it to
      take longer to finish.
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 25 Sep 2012 07:25:37 +0200
Superseded in precise-updates on 2012-10-26
Deleted in precise-proposed on 2012-10-27 (Reason: moved to -updates)
postgresql-9.1 (9.1.6-0ubuntu12.04) precise-proposed; urgency=low

  * New upstream bug fix release: (LP: #1055944)
    - Fix persistence marking of shared buffers during WAL replay.
      This mistake can result in buffers not being written out during
      checkpoints, resulting in data corruption if the server later
      crashes without ever having written those buffers. Corruption can
      occur on any server following crash recovery, but it is
      significantly more likely to occur on standby slave servers since
      those perform much more WAL replay. There is a low probability of
      corruption of btree and GIN indexes. There is a much higher
      probability of corruption of table "visibility maps". Fortunately,
      visibility maps are non-critical data in 9.1, so the worst
      consequence of such corruption in 9.1 installations is transient
      inefficiency of vacuuming. Table data proper cannot be corrupted by
      this bug.
      While no index corruption due to this bug is known to have occurred
      in the field, as a precautionary measure it is recommended that
      production installations "REINDEX" all btree and GIN indexes at a
      convenient time after upgrading to 9.1.6.
      Also, if you intend to do an in-place upgrade to 9.2.X, before
      doing so it is recommended to perform a "VACUUM" of all tables
      while having vacuum_freeze_table_age set to zero. This will ensure
      that any lingering wrong data in the visibility maps is corrected
      before 9.2.X can depend on it. vacuum_cost_delay can be adjusted to
      reduce the performance impact of vacuuming, while causing it to
      take longer to finish.
    - See HISTORY/changelog.gz for the other bug fixes.
 -- Martin Pitt <email address hidden>   Tue, 25 Sep 2012 07:21:13 +0200
Superseded in quantal-release on 2012-09-28
Deleted in quantal-proposed on 2012-09-29 (Reason: moved to release)
postgresql-9.1 (9.1.5-2) unstable; urgency=low


  * debian/rules: Re-enable hardening functions (regression from 9.1.3-2 when
    hardening-wrapper is not installed). Use "hardening=all", but disable
    "pie" (as that's not compatible with -fPIC) and add -pie to CFLAGS
    explicitly. Also drop the explicit "-Wl,-z,now" linker option, as this is
    now implied with "all". (LP: #1039618)
  * Fix upgrades from older 9.1 releases in stable Ubuntu -updates/-security
    releasese. The strict "<< 9.1.4-2~" check for moving pg_basebackup.1.gz is
    not sufficient, as Ubuntu stables have newer upstream releases by now.
    - debian/control: Move Breaks/Replaces: from static version to
      ${binary:Version}.
    - debian/postgresql-9.1.preinst: Also fix the alternatives when upgrading
      from a -0something version.
    - (LP: #1043449)

 -- Martin Pitt <email address hidden>  Fri, 31 Aug 2012 09:54:27 +0200

Available diffs

Superseded in quantal-release on 2012-09-03
postgresql-9.1 (9.1.5-1) unstable; urgency=medium


  * Urgency medium due to security fixes and bug fixes which should reach
    Wheezy quickly.
  * New upstream bug fix/security release:
    - Prevent access to external files/URLs via XML entity references.
      xml_parse() would attempt to fetch external files or URLs as needed
      to resolve DTD and entity references in an XML value, thus allowing
      unprivileged database users to attempt to fetch data with the
      privileges of the database server. While the external data wouldn't
      get returned directly to the user, portions of it could be exposed
      in error messages if the data didn't parse as valid XML; and in any
      case the mere ability to check existence of a file might be useful
      to an attacker. (CVE-2012-3489)
    - Prevent access to external files/URLs via "contrib/xml2"'s
      xslt_process().
      libxslt offers the ability to read and write both files and URLs
      through stylesheet commands, thus allowing unprivileged database
      users to both read and write data with the privileges of the
      database server. Disable that through proper use of libxslt's
      security options. (CVE-2012-3488)
      Also, remove xslt_process()'s ability to fetch documents and
      stylesheets from external files/URLs. While this was a documented
      "feature", it was long regarded as a bad idea. The fix for
      CVE-2012-3489 broke that capability, and rather than expend effort
      on trying to fix it, we're just going to summarily remove it.
    - Lots of other bug fixes, see HISTORY/changelog.gz.

 -- Martin Pitt <email address hidden>  Fri, 17 Aug 2012 14:41:52 +0200

Available diffs

Superseded in oneiric-updates on 2012-10-01
Superseded in oneiric-security on 2013-02-12
postgresql-9.1 (9.1.5-0ubuntu11.10) oneiric-security; urgency=low

  * New upstream bug fix/security release:
   - Prevent access to external files/URLs via XML entity references
     (Noah Misch, Tom Lane)
     xml_parse() would attempt to fetch external files or URLs as needed
     to resolve DTD and entity references in an XML value, thus allowing
     unprivileged database users to attempt to fetch data with the
     privileges of the database server. While the external data wouldn't
     get returned directly to the user, portions of it could be exposed
     in error messages if the data didn't parse as valid XML; and in any
     case the mere ability to check existence of a file might be useful
     to an attacker. (CVE-2012-3489)
   - Prevent access to external files/URLs via "contrib/xml2"'s
     xslt_process() (Peter Eisentraut)
     libxslt offers the ability to read and write both files and URLs
     through stylesheet commands, thus allowing unprivileged database
     users to both read and write data with the privileges of the
     database server. Disable that through proper use of libxslt's
     security options. (CVE-2012-3488)
     Also, remove xslt_process()'s ability to fetch documents and
     stylesheets from external files/URLs. While this was a documented
     "feature", it was long regarded as a bad idea. The fix for
     CVE-2012-3489 broke that capability, and rather than expend effort
     on trying to fix it, we're just going to summarily remove it.
   - Prevent too-early recycling of btree index pages (Noah Misch)
     When we allowed read-only transactions to skip assigning XIDs, we
     introduced the possibility that a deleted btree page could be
     recycled while a read-only transaction was still in flight to it.
     This would result in incorrect index search results. The
     probability of such an error occurring in the field seems very low
     because of the timing requirements, but nonetheless it should be
     fixed.
   - Fix crash-safety bug with newly-created-or-reset sequences (Tom
     Lane)
     If "ALTER SEQUENCE" was executed on a freshly created or reset
     sequence, and then precisely one nextval() call was made on it, and
     then the server crashed, WAL replay would restore the sequence to a
     state in which it appeared that no nextval() had been done, thus
     allowing the first sequence value to be returned again by the next
     nextval() call. In particular this could manifest for serial
     columns, since creation of a serial column's sequence includes an
     "ALTER SEQUENCE OWNED BY" step.
   - Fix race condition in enum-type value comparisons (Robert Haas, Tom
     Lane)
     Comparisons could fail when encountering an enum value added since
     the current query started.
   - Fix txid_current() to report the correct epoch when not in hot
     standby (Heikki Linnakangas)
     This fixes a regression introduced in the previous minor release.
   - Prevent selection of unsuitable replication connections as the
     synchronous standby (Fujii Masao)
     The master might improperly choose pseudo-servers such as
     pg_receivexlog or pg_basebackup as the synchronous standby, and
     then wait indefinitely for them.
   - Fix bug in startup of Hot Standby when a master transaction has
     many subtransactions (Andres Freund)
     This mistake led to failures reported as "out-of-order XID
     insertion in KnownAssignedXids".
   - Ensure the "backup_label" file is fsync'd after pg_start_backup()
     (Dave Kerr)
   - Fix timeout handling in walsender processes (Tom Lane)
     WAL sender background processes neglected to establish a SIGALRM
     handler, meaning they would wait forever in some corner cases where
     a timeout ought to happen.
   - Wake walsenders after each background flush by walwriter (Andres
     Freund, Simon Riggs)
     This greatly reduces replication delay when the workload contains
     only asynchronously-committed transactions.
   - Fix LISTEN/NOTIFY to cope better with I/O problems, such as out of
     disk space (Tom Lane)
     After a write failure, all subsequent attempts to send more NOTIFY
     messages would fail with messages like "Could not read from file
     "pg_notify/nnnn" at offset nnnnn: Success".
   - Only allow autovacuum to be auto-canceled by a directly blocked
     process (Tom Lane)
     The original coding could allow inconsistent behavior in some
     cases; in particular, an autovacuum could get canceled after less
     than deadlock_timeout grace period.
   - Improve logging of autovacuum cancels (Robert Haas)
   - Fix log collector so that log_truncate_on_rotation works during the
     very first log rotation after server start (Tom Lane)
   - Fix WITH attached to a nested set operation
     (UNION/INTERSECT/EXCEPT) (Tom Lane)
   - Ensure that a whole-row reference to a subquery doesn't include any
     extra GROUP BY or ORDER BY columns (Tom Lane)
   - Fix dependencies generated during ALTER TABLE ... ADD CONSTRAINT
     USING INDEX (Tom Lane)
     This command left behind a redundant pg_depend entry for the index,
     which could confuse later operations, notably ALTER TABLE ... ALTER
     COLUMN TYPE on one of the indexed columns.
   - Fix "REASSIGN OWNED" to work on extensions (Alvaro Herrera)
   - Disallow copying whole-row references in CHECK constraints and
     index definitions during "CREATE TABLE" (Tom Lane)
     This situation can arise in "CREATE TABLE" with LIKE or INHERITS.
     The copied whole-row variable was incorrectly labeled with the row
     type of the original table not the new one. Rejecting the case
     seems reasonable for LIKE, since the row types might well diverge
     later. For INHERITS we should ideally allow it, with an implicit
     coercion to the parent table's row type; but that will require more
     work than seems safe to back-patch.
   - Fix memory leak in ARRAY(SELECT ...) subqueries (Heikki
     Linnakangas, Tom Lane)
   - Fix planner to pass correct collation to operator selectivity
     estimators (Tom Lane)
     This was not previously required by any core selectivity estimation
     function, but third-party code might need it.
   - Fix extraction of common prefixes from regular expressions (Tom
     Lane)
     The code could get confused by quantified parenthesized
     subexpressions, such as ^(foo)?bar. This would lead to incorrect
     index optimization of searches for such patterns.
   - Fix bugs with parsing signed "hh":"mm" and "hh":"mm":"ss" fields in
     interval constants (Amit Kapila, Tom Lane)
   - Fix pg_dump to better handle views containing partial GROUP BY
     lists (Tom Lane)
     A view that lists only a primary key column in GROUP BY, but uses
     other table columns as if they were grouped, gets marked as
     depending on the primary key. Improper handling of such primary key
     dependencies in pg_dump resulted in poorly-ordered dumps, which at
     best would be inefficient to restore and at worst could result in
     outright failure of a parallel pg_restore run.
   - In PL/Perl, avoid setting UTF8 flag when in SQL_ASCII encoding
     (Alex Hunsaker, Kyotaro Horiguchi, Alvaro Herrera)
   - Use Postgres' encoding conversion functions, not Python's, when
     converting a Python Unicode string to the server encoding in
     PL/Python (Jan Urbanski)
     This avoids some corner-case problems, notably that Python doesn't
     support all the encodings Postgres does. A notable functional
     change is that if the server encoding is SQL_ASCII, you will get
     the UTF-8 representation of the string; formerly, any non-ASCII
     characters in the string would result in an error.
   - Fix mapping of PostgreSQL encodings to Python encodings in
     PL/Python (Jan Urbanski)
   - Report errors properly in "contrib/xml2"'s xslt_process() (Tom
     Lane)
   - Update time zone data files to tzdata release 2012e for DST law
     changes in Morocco and Tokelau
 -- Jamie Strandboge <email address hidden>   Thu, 16 Aug 2012 17:06:20 -0500
Superseded in precise-updates on 2012-10-01
Superseded in precise-security on 2013-02-12
postgresql-9.1 (9.1.5-0ubuntu12.04) precise-security; urgency=low

  * New upstream bug fix/security release:
   - Prevent access to external files/URLs via XML entity references
     (Noah Misch, Tom Lane)
     xml_parse() would attempt to fetch external files or URLs as needed
     to resolve DTD and entity references in an XML value, thus allowing
     unprivileged database users to attempt to fetch data with the
     privileges of the database server. While the external data wouldn't
     get returned directly to the user, portions of it could be exposed
     in error messages if the data didn't parse as valid XML; and in any
     case the mere ability to check existence of a file might be useful
     to an attacker. (CVE-2012-3489)
   - Prevent access to external files/URLs via "contrib/xml2"'s
     xslt_process() (Peter Eisentraut)
     libxslt offers the ability to read and write both files and URLs
     through stylesheet commands, thus allowing unprivileged database
     users to both read and write data with the privileges of the
     database server. Disable that through proper use of libxslt's
     security options. (CVE-2012-3488)
     Also, remove xslt_process()'s ability to fetch documents and
     stylesheets from external files/URLs. While this was a documented
     "feature", it was long regarded as a bad idea. The fix for
     CVE-2012-3489 broke that capability, and rather than expend effort
     on trying to fix it, we're just going to summarily remove it.
   - Prevent too-early recycling of btree index pages (Noah Misch)
     When we allowed read-only transactions to skip assigning XIDs, we
     introduced the possibility that a deleted btree page could be
     recycled while a read-only transaction was still in flight to it.
     This would result in incorrect index search results. The
     probability of such an error occurring in the field seems very low
     because of the timing requirements, but nonetheless it should be
     fixed.
   - Fix crash-safety bug with newly-created-or-reset sequences (Tom
     Lane)
     If "ALTER SEQUENCE" was executed on a freshly created or reset
     sequence, and then precisely one nextval() call was made on it, and
     then the server crashed, WAL replay would restore the sequence to a
     state in which it appeared that no nextval() had been done, thus
     allowing the first sequence value to be returned again by the next
     nextval() call. In particular this could manifest for serial
     columns, since creation of a serial column's sequence includes an
     "ALTER SEQUENCE OWNED BY" step.
   - Fix race condition in enum-type value comparisons (Robert Haas, Tom
     Lane)
     Comparisons could fail when encountering an enum value added since
     the current query started.
   - Fix txid_current() to report the correct epoch when not in hot
     standby (Heikki Linnakangas)
     This fixes a regression introduced in the previous minor release.
   - Prevent selection of unsuitable replication connections as the
     synchronous standby (Fujii Masao)
     The master might improperly choose pseudo-servers such as
     pg_receivexlog or pg_basebackup as the synchronous standby, and
     then wait indefinitely for them.
   - Fix bug in startup of Hot Standby when a master transaction has
     many subtransactions (Andres Freund)
     This mistake led to failures reported as "out-of-order XID
     insertion in KnownAssignedXids".
   - Ensure the "backup_label" file is fsync'd after pg_start_backup()
     (Dave Kerr)
   - Fix timeout handling in walsender processes (Tom Lane)
     WAL sender background processes neglected to establish a SIGALRM
     handler, meaning they would wait forever in some corner cases where
     a timeout ought to happen.
   - Wake walsenders after each background flush by walwriter (Andres
     Freund, Simon Riggs)
     This greatly reduces replication delay when the workload contains
     only asynchronously-committed transactions.
   - Fix LISTEN/NOTIFY to cope better with I/O problems, such as out of
     disk space (Tom Lane)
     After a write failure, all subsequent attempts to send more NOTIFY
     messages would fail with messages like "Could not read from file
     "pg_notify/nnnn" at offset nnnnn: Success".
   - Only allow autovacuum to be auto-canceled by a directly blocked
     process (Tom Lane)
     The original coding could allow inconsistent behavior in some
     cases; in particular, an autovacuum could get canceled after less
     than deadlock_timeout grace period.
   - Improve logging of autovacuum cancels (Robert Haas)
   - Fix log collector so that log_truncate_on_rotation works during the
     very first log rotation after server start (Tom Lane)
   - Fix WITH attached to a nested set operation
     (UNION/INTERSECT/EXCEPT) (Tom Lane)
   - Ensure that a whole-row reference to a subquery doesn't include any
     extra GROUP BY or ORDER BY columns (Tom Lane)
   - Fix dependencies generated during ALTER TABLE ... ADD CONSTRAINT
     USING INDEX (Tom Lane)
     This command left behind a redundant pg_depend entry for the index,
     which could confuse later operations, notably ALTER TABLE ... ALTER
     COLUMN TYPE on one of the indexed columns.
   - Fix "REASSIGN OWNED" to work on extensions (Alvaro Herrera)
   - Disallow copying whole-row references in CHECK constraints and
     index definitions during "CREATE TABLE" (Tom Lane)
     This situation can arise in "CREATE TABLE" with LIKE or INHERITS.
     The copied whole-row variable was incorrectly labeled with the row
     type of the original table not the new one. Rejecting the case
     seems reasonable for LIKE, since the row types might well diverge
     later. For INHERITS we should ideally allow it, with an implicit
     coercion to the parent table's row type; but that will require more
     work than seems safe to back-patch.
   - Fix memory leak in ARRAY(SELECT ...) subqueries (Heikki
     Linnakangas, Tom Lane)
   - Fix planner to pass correct collation to operator selectivity
     estimators (Tom Lane)
     This was not previously required by any core selectivity estimation
     function, but third-party code might need it.
   - Fix extraction of common prefixes from regular expressions (Tom
     Lane)
     The code could get confused by quantified parenthesized
     subexpressions, such as ^(foo)?bar. This would lead to incorrect
     index optimization of searches for such patterns.
   - Fix bugs with parsing signed "hh":"mm" and "hh":"mm":"ss" fields in
     interval constants (Amit Kapila, Tom Lane)
   - Fix pg_dump to better handle views containing partial GROUP BY
     lists (Tom Lane)
     A view that lists only a primary key column in GROUP BY, but uses
     other table columns as if they were grouped, gets marked as
     depending on the primary key. Improper handling of such primary key
     dependencies in pg_dump resulted in poorly-ordered dumps, which at
     best would be inefficient to restore and at worst could result in
     outright failure of a parallel pg_restore run.
   - In PL/Perl, avoid setting UTF8 flag when in SQL_ASCII encoding
     (Alex Hunsaker, Kyotaro Horiguchi, Alvaro Herrera)
   - Use Postgres' encoding conversion functions, not Python's, when
     converting a Python Unicode string to the server encoding in
     PL/Python (Jan Urbanski)
     This avoids some corner-case problems, notably that Python doesn't
     support all the encodings Postgres does. A notable functional
     change is that if the server encoding is SQL_ASCII, you will get
     the UTF-8 representation of the string; formerly, any non-ASCII
     characters in the string would result in an error.
   - Fix mapping of PostgreSQL encodings to Python encodings in
     PL/Python (Jan Urbanski)
   - Report errors properly in "contrib/xml2"'s xslt_process() (Tom
     Lane)
   - Update time zone data files to tzdata release 2012e for DST law
     changes in Morocco and Tokelau
 -- Jamie Strandboge <email address hidden>   Thu, 16 Aug 2012 16:49:18 -0500
Superseded in quantal-release on 2012-08-19
postgresql-9.1 (9.1.4-3) unstable; urgency=medium


  Urgency medium: Trivial changes, and fixes RC bug.

  [ Christoph Berg ]
  * debian/source/options: Ignore test suite .sql files, to fix building
    twice in a row; ignore .bzr-builddeb/default.conf so bzr checkouts can be
    built using dpkg-buildpackage.

  [ Martin Pitt ]
  * debian/postgresql-9.1.postrm: Do not remove the directories
    /var/{lib,log}/postgresql/, they are owned by the postgresql-common
    package. (Closes: #681966)

 -- Martin Pitt <email address hidden>  Sat, 21 Jul 2012 16:53:55 +0200

Available diffs

Superseded in quantal-release on 2012-07-28
postgresql-9.1 (9.1.4-2) unstable; urgency=low


  [ Christoph Berg ]
  * Some cosmetic changes to control and rules file.
  * Add myself to Uploaders.

  [ Martin Pitt ]
  * Move pg_basebackup *.mo files and man page to -client-9.2. Thanks to Peter
    Eisentraut for spotting this. (Closes: #674421)
  * debian/postgresql-9.1.preinst: Remove postmaster.1.gz alternative on
    upgrades to this version, so that the postinst can rebuild it. This is
    necessary to drop pg_basebackup.1.gz from the server alternatives group,
    so that it can go into the client group.
  * debian/postgresql-9.1.preinst: Drop obsolete transition code.
  * debian/rules: Set -DLINUX_OOM_ADJ in CPPFLAGS, not in CFLAGS. Thanks Peter
    Eisentraut. (Closes: #668300)

 -- Martin Pitt <email address hidden>  Fri, 22 Jun 2012 10:35:38 +0200

Available diffs

Superseded in quantal-release on 2012-06-23
postgresql-9.1 (9.1.4-1) unstable; urgency=medium


  * Urgency medium due to security fixes.
  * New upstream bug fix/security release:
    - Fix incorrect password transformation in "contrib/pgcrypto"'s DES
      crypt() function.
      If a password string contained the byte value 0x80, the remainder
      of the password was ignored, causing the password to be much weaker
      than it appeared. With this fix, the rest of the string is properly
      included in the DES hash. Any stored password values that are
      affected by this bug will thus no longer match, so the stored
      values may need to be updated. (CVE-2012-2143)
    - Ignore SECURITY DEFINER and SET attributes for a procedural
      language's call handler. Applying such attributes to a call handler
      could crash the server. (CVE-2012-2655)
    - Make "contrib/citext"'s upgrade script fix collations of citext
      arrays and domains over citext.
      Release 9.1.2 provided a fix for collations of citext columns and
      indexes in databases upgraded or reloaded from pre-9.1
      installations, but that fix was incomplete: it neglected to handle
      arrays and domains over citext. This release extends the module's
      upgrade script to handle these cases. As before, if you have
      already run the upgrade script, you'll need to run the collation
      update commands by hand instead. See the 9.1.2 release notes for
      more information about doing this.
    - Allow numeric timezone offsets in timestamp input to be up to 16
      hours away from UTC. Some historical time zones have offsets larger than
      15 hours, the previous limit. This could result in dumped data values
      being rejected during reload.
    - Fix timestamp conversion to cope when the given time is exactly the
      last DST transition time for the current timezone.
      This oversight has been there a long time, but was not noticed
      previously because most DST-using zones are presumed to have an
      indefinite sequence of future DST transitions.
    - Fix text to name and char to name casts to perform string
      truncation correctly in multibyte encodings.
    - Fix memory copying bug in to_tsquery().
    - Ensure txid_current() reports the correct epoch when executed in
      hot standby.
    - Fix planner's handling of outer PlaceHolderVars within subqueries.
      This bug concerns sub-SELECTs that reference variables coming from
      the nullable side of an outer join of the surrounding query. In
      9.1, queries affected by this bug would fail with "ERROR:
      Upper-level PlaceHolderVar found where not expected". But in 9.0
      and 8.4, you'd silently get possibly-wrong answers, since the value
      transmitted into the subquery wouldn't go to null when it should.
    - Fix planning of UNION ALL subqueries with output columns that are
      not simple variables.
      Planning of such cases got noticeably worse in 9.1 as a result of a
      misguided fix for "MergeAppend child's targetlist doesn't match
      MergeAppend" errors. Revert that fix and do it another way.
    - Fix slow session startup when pg_attribute is very large.
      If pg_attribute exceeds one-fourth of shared_buffers, cache
      rebuilding code that is sometimes needed during session start would
      trigger the synchronized-scan logic, causing it to take many times
      longer than normal. The problem was particularly acute if many new
      sessions were starting at once.
    - Ensure sequential scans check for query cancel reasonably often.
      A scan encountering many consecutive pages that contain no live
      tuples would not respond to interrupts meanwhile.
    - Ensure the Windows implementation of PGSemaphoreLock() clears
      ImmediateInterruptOK before returning.
      This oversight meant that a query-cancel interrupt received later
      in the same query could be accepted at an unsafe time, with
      unpredictable but not good consequences.
    - Show whole-row variables safely when printing views or rules.
      Corner cases involving ambiguous names (that is, the name could be
      either a table or column name of the query) were printed in an
      ambiguous way, risking that the view or rule would be interpreted
      differently after dump and reload. Avoid the ambiguous case by
      attaching a no-op cast.
    - Fix "COPY FROM" to properly handle null marker strings that
      correspond to invalid encoding.
      A null marker string such as E'\\0' should work, and did work in
      the past, but the case got broken in 8.4.
    - Fix "EXPLAIN VERBOSE" for writable CTEs containing RETURNING
      clauses.
    - Fix "PREPARE TRANSACTION" to work correctly in the presence of
      advisory locks.
      Historically, "PREPARE TRANSACTION" has simply ignored any
      session-level advisory locks the session holds, but this case was
      accidentally broken in 9.1.
    - Fix truncation of unlogged tables.
    - Ignore missing schemas during non-interactive assignments of
      search_path.
      This re-aligns 9.1's behavior with that of older branches.
      Previously 9.1 would throw an error for nonexistent schemas
      mentioned in search_path settings obtained from places such as
      "ALTER DATABASE SET".
    - Fix bugs with temporary or transient tables used in extension
      scripts.
      This includes cases such as a rewriting "ALTER TABLE" within an
      extension update script, since that uses a transient table behind
      the scenes.
    - Ensure autovacuum worker processes perform stack depth checking
      properly.
      Previously, infinite recursion in a function invoked by
      auto-"ANALYZE" could crash worker processes.
    - Fix logging collector to not lose log coherency under high load.
      The collector previously could fail to reassemble large messages if
      it got too busy.
    - Fix logging collector to ensure it will restart file rotation after
      receiving SIGHUP.
    - Fix "too many LWLocks taken" failure in GiST indexes.
    - Fix WAL replay logic for GIN indexes to not fail if the index was
      subsequently dropped.
    - Correctly detect SSI conflicts of prepared transactions after a
      crash.
    - Avoid synchronous replication delay when committing a transaction
      that only modified temporary tables.
      In such a case the transaction's commit record need not be flushed
      to standby servers, but some of the code didn't know that and
      waited for it to happen anyway.
    - Fix error handling in pg_basebackup.
    - Fix walsender to not go into a busy loop if connection is
      terminated.
    - Fix memory leak in PL/pgSQL's "RETURN NEXT" command.
    - Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
      function's first variable.
    - Ensure that PL/Perl package-qualifies the _TD variable.
      This bug caused trigger invocations to fail when they are nested
      within a function invocation that changes the current package.
    - Fix PL/Python functions returning composite types to accept a
      string for their result value.
      This case was accidentally broken by the 9.1 additions to allow a
      composite result value to be supplied in other formats, such as
      dictionaries.
    - Fix potential access off the end of memory in psql's expanded
      display ("\x") mode.
    - Fix several performance problems in pg_dump when the database
      contains many objects.
      pg_dump could get very slow if the database contained many schemas,
      or if many objects are in dependency loops, or if there are many
      owned sequences.
    - Fix memory and file descriptor leaks in pg_restore when reading a
      directory-format archive.
    - Fix pg_upgrade for the case that a database stored in a non-default
      tablespace contains a table in the cluster's default tablespace.
    - In ecpg, fix rare memory leaks and possible overwrite of one byte
      after the sqlca_t structure.
    - Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
      connections upon error.
    - Fix "contrib/dblink" to report the correct connection name in error
      messages.
    - Fix "contrib/vacuumlo" to use multiple transactions when dropping
      many large objects.
      This change avoids exceeding max_locks_per_transaction when many
      objects need to be dropped. The behavior can be adjusted with the
      new -l (limit) option.
  * debian/control: Bump debhelper build dependency to >= 8, as it does not
    build with earlier versions.
  * debian/control: Move bzr branches to alioth, so that other members of
    pkg-postgresql can commit. Update Vcs-* tags.
  * debian/control: Set Maintainer: to pkg-postgresql group, and move myself
    to Uploaders:.

 -- Martin Pitt <email address hidden>  Mon, 04 Jun 2012 06:47:45 +0200

Available diffs

Superseded in oneiric-updates on 2012-08-20
Superseded in oneiric-security on 2012-08-20
postgresql-9.1 (9.1.4-0ubuntu11.10) oneiric-security; urgency=low

  * New upstream bug fix/security release: (LP: #1008317)
    - Fix incorrect password transformation in "contrib/pgcrypto"'s DES
      crypt() function.
      If a password string contained the byte value 0x80, the remainder
      of the password was ignored, causing the password to be much weaker
      than it appeared. With this fix, the rest of the string is properly
      included in the DES hash. Any stored password values that are
      affected by this bug will thus no longer match, so the stored
      values may need to be updated. (CVE-2012-2143)
    - Ignore SECURITY DEFINER and SET attributes for a procedural
      language's call handler. Applying such attributes to a call handler
      could crash the server. (CVE-2012-2655)
    - Make "contrib/citext"'s upgrade script fix collations of citext
      arrays and domains over citext.
      Release 9.1.2 provided a fix for collations of citext columns and
      indexes in databases upgraded or reloaded from pre-9.1
      installations, but that fix was incomplete: it neglected to handle
      arrays and domains over citext. This release extends the module's
      upgrade script to handle these cases. As before, if you have
      already run the upgrade script, you'll need to run the collation
      update commands by hand instead. See the 9.1.2 release notes for
      more information about doing this.
    - Allow numeric timezone offsets in timestamp input to be up to 16
      hours away from UTC. Some historical time zones have offsets larger than
      15 hours, the previous limit. This could result in dumped data values
      being rejected during reload.
    - Fix timestamp conversion to cope when the given time is exactly the
      last DST transition time for the current timezone.
      This oversight has been there a long time, but was not noticed
      previously because most DST-using zones are presumed to have an
      indefinite sequence of future DST transitions.
    - Fix text to name and char to name casts to perform string
      truncation correctly in multibyte encodings.
    - Fix memory copying bug in to_tsquery().
    - Ensure txid_current() reports the correct epoch when executed in
      hot standby.
    - Fix planner's handling of outer PlaceHolderVars within subqueries.
      This bug concerns sub-SELECTs that reference variables coming from
      the nullable side of an outer join of the surrounding query. In
      9.1, queries affected by this bug would fail with "ERROR:
      Upper-level PlaceHolderVar found where not expected". But in 9.0
      and 8.4, you'd silently get possibly-wrong answers, since the value
      transmitted into the subquery wouldn't go to null when it should.
    - Fix planning of UNION ALL subqueries with output columns that are
      not simple variables.
      Planning of such cases got noticeably worse in 9.1 as a result of a
      misguided fix for "MergeAppend child's targetlist doesn't match
      MergeAppend" errors. Revert that fix and do it another way.
    - Fix slow session startup when pg_attribute is very large.
      If pg_attribute exceeds one-fourth of shared_buffers, cache
      rebuilding code that is sometimes needed during session start would
      trigger the synchronized-scan logic, causing it to take many times
      longer than normal. The problem was particularly acute if many new
      sessions were starting at once.
    - Ensure sequential scans check for query cancel reasonably often.
      A scan encountering many consecutive pages that contain no live
      tuples would not respond to interrupts meanwhile.
    - Ensure the Windows implementation of PGSemaphoreLock() clears
      ImmediateInterruptOK before returning.
      This oversight meant that a query-cancel interrupt received later
      in the same query could be accepted at an unsafe time, with
      unpredictable but not good consequences.
    - Show whole-row variables safely when printing views or rules.
      Corner cases involving ambiguous names (that is, the name could be
      either a table or column name of the query) were printed in an
      ambiguous way, risking that the view or rule would be interpreted
      differently after dump and reload. Avoid the ambiguous case by
      attaching a no-op cast.
    - Fix "COPY FROM" to properly handle null marker strings that
      correspond to invalid encoding.
      A null marker string such as E'\\0' should work, and did work in
      the past, but the case got broken in 8.4.
    - Fix "EXPLAIN VERBOSE" for writable CTEs containing RETURNING
      clauses.
    - Fix "PREPARE TRANSACTION" to work correctly in the presence of
      advisory locks.
      Historically, "PREPARE TRANSACTION" has simply ignored any
      session-level advisory locks the session holds, but this case was
      accidentally broken in 9.1.
    - Fix truncation of unlogged tables.
    - Ignore missing schemas during non-interactive assignments of
      search_path.
      This re-aligns 9.1's behavior with that of older branches.
      Previously 9.1 would throw an error for nonexistent schemas
      mentioned in search_path settings obtained from places such as
      "ALTER DATABASE SET".
    - Fix bugs with temporary or transient tables used in extension
      scripts.
      This includes cases such as a rewriting "ALTER TABLE" within an
      extension update script, since that uses a transient table behind
      the scenes.
    - Ensure autovacuum worker processes perform stack depth checking
      properly.
      Previously, infinite recursion in a function invoked by
      auto-"ANALYZE" could crash worker processes.
    - Fix logging collector to not lose log coherency under high load.
      The collector previously could fail to reassemble large messages if
      it got too busy.
    - Fix logging collector to ensure it will restart file rotation after
      receiving SIGHUP.
    - Fix "too many LWLocks taken" failure in GiST indexes.
    - Fix WAL replay logic for GIN indexes to not fail if the index was
      subsequently dropped.
    - Correctly detect SSI conflicts of prepared transactions after a
      crash.
    - Avoid synchronous replication delay when committing a transaction
      that only modified temporary tables.
      In such a case the transaction's commit record need not be flushed
      to standby servers, but some of the code didn't know that and
      waited for it to happen anyway.
    - Fix error handling in pg_basebackup.
    - Fix walsender to not go into a busy loop if connection is
      terminated.
    - Fix memory leak in PL/pgSQL's "RETURN NEXT" command.
    - Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
      function's first variable.
    - Ensure that PL/Perl package-qualifies the _TD variable.
      This bug caused trigger invocations to fail when they are nested
      within a function invocation that changes the current package.
    - Fix PL/Python functions returning composite types to accept a
      string for their result value.
      This case was accidentally broken by the 9.1 additions to allow a
      composite result value to be supplied in other formats, such as
      dictionaries.
    - Fix potential access off the end of memory in psql's expanded
      display ("\x") mode.
    - Fix several performance problems in pg_dump when the database
      contains many objects.
      pg_dump could get very slow if the database contained many schemas,
      or if many objects are in dependency loops, or if there are many
      owned sequences.
    - Fix memory and file descriptor leaks in pg_restore when reading a
      directory-format archive.
    - Fix pg_upgrade for the case that a database stored in a non-default
      tablespace contains a table in the cluster's default tablespace.
    - In ecpg, fix rare memory leaks and possible overwrite of one byte
      after the sqlca_t structure.
    - Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
      connections upon error.
    - Fix "contrib/dblink" to report the correct connection name in error
      messages.
    - Fix "contrib/vacuumlo" to use multiple transactions when dropping
      many large objects.
      This change avoids exceeding max_locks_per_transaction when many
      objects need to be dropped. The behavior can be adjusted with the
      new -l (limit) option.
 -- Martin Pitt <email address hidden>   Mon, 04 Jun 2012 08:03:17 +0200
Superseded in precise-updates on 2012-08-20
Superseded in precise-security on 2012-08-20
postgresql-9.1 (9.1.4-0ubuntu12.04) precise-security; urgency=low

  * New upstream bug fix/security release: (LP: #1008317)
    - Fix incorrect password transformation in "contrib/pgcrypto"'s DES
      crypt() function.
      If a password string contained the byte value 0x80, the remainder
      of the password was ignored, causing the password to be much weaker
      than it appeared. With this fix, the rest of the string is properly
      included in the DES hash. Any stored password values that are
      affected by this bug will thus no longer match, so the stored
      values may need to be updated. (CVE-2012-2143)
    - Ignore SECURITY DEFINER and SET attributes for a procedural
      language's call handler. Applying such attributes to a call handler
      could crash the server. (CVE-2012-2655)
    - Make "contrib/citext"'s upgrade script fix collations of citext
      arrays and domains over citext.
      Release 9.1.2 provided a fix for collations of citext columns and
      indexes in databases upgraded or reloaded from pre-9.1
      installations, but that fix was incomplete: it neglected to handle
      arrays and domains over citext. This release extends the module's
      upgrade script to handle these cases. As before, if you have
      already run the upgrade script, you'll need to run the collation
      update commands by hand instead. See the 9.1.2 release notes for
      more information about doing this.
    - Allow numeric timezone offsets in timestamp input to be up to 16
      hours away from UTC. Some historical time zones have offsets larger than
      15 hours, the previous limit. This could result in dumped data values
      being rejected during reload.
    - Fix timestamp conversion to cope when the given time is exactly the
      last DST transition time for the current timezone.
      This oversight has been there a long time, but was not noticed
      previously because most DST-using zones are presumed to have an
      indefinite sequence of future DST transitions.
    - Fix text to name and char to name casts to perform string
      truncation correctly in multibyte encodings.
    - Fix memory copying bug in to_tsquery().
    - Ensure txid_current() reports the correct epoch when executed in
      hot standby.
    - Fix planner's handling of outer PlaceHolderVars within subqueries.
      This bug concerns sub-SELECTs that reference variables coming from
      the nullable side of an outer join of the surrounding query. In
      9.1, queries affected by this bug would fail with "ERROR:
      Upper-level PlaceHolderVar found where not expected". But in 9.0
      and 8.4, you'd silently get possibly-wrong answers, since the value
      transmitted into the subquery wouldn't go to null when it should.
    - Fix planning of UNION ALL subqueries with output columns that are
      not simple variables.
      Planning of such cases got noticeably worse in 9.1 as a result of a
      misguided fix for "MergeAppend child's targetlist doesn't match
      MergeAppend" errors. Revert that fix and do it another way.
    - Fix slow session startup when pg_attribute is very large.
      If pg_attribute exceeds one-fourth of shared_buffers, cache
      rebuilding code that is sometimes needed during session start would
      trigger the synchronized-scan logic, causing it to take many times
      longer than normal. The problem was particularly acute if many new
      sessions were starting at once.
    - Ensure sequential scans check for query cancel reasonably often.
      A scan encountering many consecutive pages that contain no live
      tuples would not respond to interrupts meanwhile.
    - Ensure the Windows implementation of PGSemaphoreLock() clears
      ImmediateInterruptOK before returning.
      This oversight meant that a query-cancel interrupt received later
      in the same query could be accepted at an unsafe time, with
      unpredictable but not good consequences.
    - Show whole-row variables safely when printing views or rules.
      Corner cases involving ambiguous names (that is, the name could be
      either a table or column name of the query) were printed in an
      ambiguous way, risking that the view or rule would be interpreted
      differently after dump and reload. Avoid the ambiguous case by
      attaching a no-op cast.
    - Fix "COPY FROM" to properly handle null marker strings that
      correspond to invalid encoding.
      A null marker string such as E'\\0' should work, and did work in
      the past, but the case got broken in 8.4.
    - Fix "EXPLAIN VERBOSE" for writable CTEs containing RETURNING
      clauses.
    - Fix "PREPARE TRANSACTION" to work correctly in the presence of
      advisory locks.
      Historically, "PREPARE TRANSACTION" has simply ignored any
      session-level advisory locks the session holds, but this case was
      accidentally broken in 9.1.
    - Fix truncation of unlogged tables.
    - Ignore missing schemas during non-interactive assignments of
      search_path.
      This re-aligns 9.1's behavior with that of older branches.
      Previously 9.1 would throw an error for nonexistent schemas
      mentioned in search_path settings obtained from places such as
      "ALTER DATABASE SET".
    - Fix bugs with temporary or transient tables used in extension
      scripts.
      This includes cases such as a rewriting "ALTER TABLE" within an
      extension update script, since that uses a transient table behind
      the scenes.
    - Ensure autovacuum worker processes perform stack depth checking
      properly.
      Previously, infinite recursion in a function invoked by
      auto-"ANALYZE" could crash worker processes.
    - Fix logging collector to not lose log coherency under high load.
      The collector previously could fail to reassemble large messages if
      it got too busy.
    - Fix logging collector to ensure it will restart file rotation after
      receiving SIGHUP.
    - Fix "too many LWLocks taken" failure in GiST indexes.
    - Fix WAL replay logic for GIN indexes to not fail if the index was
      subsequently dropped.
    - Correctly detect SSI conflicts of prepared transactions after a
      crash.
    - Avoid synchronous replication delay when committing a transaction
      that only modified temporary tables.
      In such a case the transaction's commit record need not be flushed
      to standby servers, but some of the code didn't know that and
      waited for it to happen anyway.
    - Fix error handling in pg_basebackup.
    - Fix walsender to not go into a busy loop if connection is
      terminated.
    - Fix memory leak in PL/pgSQL's "RETURN NEXT" command.
    - Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
      function's first variable.
    - Ensure that PL/Perl package-qualifies the _TD variable.
      This bug caused trigger invocations to fail when they are nested
      within a function invocation that changes the current package.
    - Fix PL/Python functions returning composite types to accept a
      string for their result value.
      This case was accidentally broken by the 9.1 additions to allow a
      composite result value to be supplied in other formats, such as
      dictionaries.
    - Fix potential access off the end of memory in psql's expanded
      display ("\x") mode.
    - Fix several performance problems in pg_dump when the database
      contains many objects.
      pg_dump could get very slow if the database contained many schemas,
      or if many objects are in dependency loops, or if there are many
      owned sequences.
    - Fix memory and file descriptor leaks in pg_restore when reading a
      directory-format archive.
    - Fix pg_upgrade for the case that a database stored in a non-default
      tablespace contains a table in the cluster's default tablespace.
    - In ecpg, fix rare memory leaks and possible overwrite of one byte
      after the sqlca_t structure.
    - Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
      connections upon error.
    - Fix "contrib/dblink" to report the correct connection name in error
      messages.
    - Fix "contrib/vacuumlo" to use multiple transactions when dropping
      many large objects.
      This change avoids exceeding max_locks_per_transaction when many
      objects need to be dropped. The behavior can be adjusted with the
      new -l (limit) option.
 -- Martin Pitt <email address hidden>   Mon, 04 Jun 2012 06:31:48 +0200
Superseded in quantal-release on 2012-06-08
Published in precise-release on 2012-03-06
postgresql-9.1 (9.1.3-2) unstable; urgency=low

  * debian/control, debian/rules: Support and prefer dpkg-buildflags when
    building with dpkg-dev >= 1.16.1~. Fall back to hardening-wrapper
    otherwise, to keep supporting backports.
  * debian/rules: Build with "-z now" for some extra hardening. We can't use
    the full "hardening=+all", as PIE causes build failures.
  * debian/copyright: Fix syntax for copyright format 1.0.
  * debian/control: Bump Breaks/Replaces versions to current binary version,
    so that e. g. the moved pg_basebackup does not cause upgrade errors when
    upgrading from higher point releases in previous distro releases.
    (LP: #944632)
 -- Martin Pitt <email address hidden>   Tue, 06 Mar 2012 11:55:57 +0100

Available diffs

Superseded in precise-release on 2012-03-06
postgresql-9.1 (9.1.3-1) unstable; urgency=medium


  * Urgency medium due to security fixes.
  * New upstream security/bug fix release:
    - Require execute permission on the trigger function for "CREATE
      TRIGGER".
      This missing check could allow another user to execute a trigger
      function with forged input data, by installing it on a table he
      owns. This is only of significance for trigger functions marked
      SECURITY DEFINER, since otherwise trigger functions run as the
      table owner anyway. (CVE-2012-0866)
    - Remove arbitrary limitation on length of common name in SSL
      certificates.
      Both libpq and the server truncated the common name extracted from
      an SSL certificate at 32 bytes. Normally this would cause nothing
      worse than an unexpected verification failure, but there are some
      rather-implausible scenarios in which it might allow one
      certificate holder to impersonate another. The victim would have to
      have a common name exactly 32 bytes long, and the attacker would
      have to persuade a trusted CA to issue a certificate in which the
      common name has that string as a prefix. Impersonating a server
      would also require some additional exploit to redirect client
      connections. (CVE-2012-0867)
    - Convert newlines to spaces in names written in pg_dump comments.
      pg_dump was incautious about sanitizing object names that are
      emitted within SQL comments in its output script. A name containing
      a newline would at least render the script syntactically incorrect.
      Maliciously crafted object names could present a SQL injection risk
      when the script is reloaded. (CVE-2012-0868)
    - Fix btree index corruption from insertions concurrent with
      vacuuming.
      An index page split caused by an insertion could sometimes cause a
      concurrently-running "VACUUM" to miss removing index entries that
      it should remove. After the corresponding table rows are removed,
      the dangling index entries would cause errors (such as "could not
      read block N in file ...") or worse, silently wrong query results
      after unrelated rows are re-inserted at the now-free table
      locations. This bug has been present since release 8.2, but occurs
      so infrequently that it was not diagnosed until now. If you have
      reason to suspect that it has happened in your database, reindexing
      the affected index will fix things.
    - Fix transient zeroing of shared buffers during WAL replay.
      The replay logic would sometimes zero and refill a shared buffer,
      so that the contents were transiently invalid. In hot standby mode
      this can result in a query that's executing in parallel seeing
      garbage data. Various symptoms could result from that, but the most
      common one seems to be "invalid memory alloc request size".
    - Fix handling of data-modifying WITH subplans in READ COMMITTED
      rechecking.
      A WITH clause containing "INSERT"/"UPDATE"/"DELETE" would crash if
      the parent "UPDATE" or "DELETE" command needed to be re-evaluated
      at one or more rows due to concurrent updates in READ COMMITTED
      mode.
    - Fix corner case in SSI transaction cleanup.
      When finishing up a read-write serializable transaction, a crash
      could occur if all remaining active serializable transactions are
      read-only.
    - Fix postmaster to attempt restart after a hot-standby crash.
      A logic error caused the postmaster to terminate, rather than
      attempt to restart the cluster, if any backend process crashed
      while operating in hot standby mode.
    - Fix "CLUSTER"/"VACUUM FULL" handling of toast values owned by
      recently-updated rows.
      This oversight could lead to "duplicate key value violates unique
      constraint" errors being reported against the toast table's index
      during one of these commands.
    - Update per-column permissions, not only per-table permissions, when
      changing table owner.
      Failure to do this meant that any previously granted column
      permissions were still shown as having been granted by the old
      owner. This meant that neither the new owner nor a superuser could
      revoke the now-untraceable-to-table-owner permissions.
    - Support foreign data wrappers and foreign servers in "REASSIGN
      OWNED".
      This command failed with "unexpected classid" errors if it needed
      to change the ownership of any such objects.
    - Allow non-existent values for some settings in "ALTER USER/DATABASE
      SET".
      Allow default_text_search_config, default_tablespace, and
      temp_tablespaces to be set to names that are not known. This is
      because they might be known in another database where the setting
      is intended to be used, or for the tablespace cases because the
      tablespace might not be created yet. The same issue was previously
      recognized for search_path, and these settings now act like that
      one.
    - Fix "unsupported node type" error caused by COLLATE in an "INSERT"
      expression.
    - Avoid crashing when we have problems deleting table files
      post-commit.
      Dropping a table should lead to deleting the underlying disk files
      only after the transaction commits. In event of failure then (for
      instance, because of wrong file permissions) the code is supposed
      to just emit a warning message and go on, since it's too late to
      abort the transaction. This logic got broken as of release 8.4,
      causing such situations to result in a PANIC and an unrestartable
      database.
    - Recover from errors occurring during WAL replay of "DROP
      TABLESPACE".
      Replay will attempt to remove the tablespace's directories, but
      there are various reasons why this might fail (for example,
      incorrect ownership or permissions on those directories). Formerly
      the replay code would panic, rendering the database unrestartable
      without manual intervention. It seems better to log the problem and
      continue, since the only consequence of failure to remove the
      directories is some wasted disk space.
    - Fix race condition in logging AccessExclusiveLocks for hot standby.
      Sometimes a lock would be logged as being held by "transaction
      zero". This is at least known to produce assertion failures on
      slave servers, and might be the cause of more serious problems.
    - Track the OID counter correctly during WAL replay, even when it
      wraps around.
    - Prevent emitting misleading "consistent recovery state reached" log
      message at the beginning of crash recovery.
    - Fix initial value of pg_stat_replication.replay_location.
    - Fix regular expression back-references with - attached.
      Rather than enforcing an exact string match, the code would
      effectively accept any string that satisfies the pattern
      sub-expression referenced by the back-reference symbol.
      A similar problem still afflicts back-references that are embedded
      in a larger quantified expression, rather than being the immediate
      subject of the quantifier. This will be addressed in a future
      PostgreSQL release.
    - Fix recently-introduced memory leak in processing of inet/cidr
      values.
    - Fix planner's ability to push down index-expression restrictions
      through UNION ALL.
    - Fix planning of WITH clauses referenced in "UPDATE"/"DELETE" on an
      inherited table.
      This bug led to "could not find plan for CTE" failures.
    - Fix GIN cost estimation to handle column IN (...) index conditions.
      This oversight would usually lead to crashes if such a condition
      could be used with a GIN index.
    - Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a
      SQL-language function.
      In most cases this only led to an assertion failure in
      assert-enabled builds, but worse consequences seem possible.
    - Fix I/O-conversion-related memory leaks in plpgsql.
    - Work around bug in perl's SvPVutf8() function.
      This function crashes when handed a typeglob or certain read-only
      objects such as $^V. Make plperl avoid passing those to it.
    - In pg_dump, don't dump contents of an extension's configuration
      tables if the extension itself is not being dumped.
    - Improve pg_dump's handling of inherited table columns.
      pg_dump mishandled situations where a child column has a different
      default expression than its parent column. If the default is
      textually identical to the parent's default, but not actually the
      same (for instance, because of schema search path differences) it
      would not be recognized as different, so that after dump and
      restore the child would be allowed to inherit the parent's default.
      Child columns that are NOT NULL where their parent is not could
      also be restored subtly incorrectly.
    - Fix pg_restore's direct-to-database mode for INSERT-style table data.
      Direct-to-database restores from archive files made with
      "--inserts" or "--column-inserts" options fail when using
      pg_restore from a release dated September or December 2011, as a
      result of an oversight in a fix for another problem. The archive
      file itself is not at fault, and text-mode output is okay.
    - Teach pg_upgrade to handle renaming of plpython's shared library.
      Upgrading a pre-9.1 database that included plpython would fail
      because of this oversight.
    - Allow pg_upgrade to process tables containing regclass columns.
      Since pg_upgrade now takes care to preserve pg_class OIDs, there
      was no longer any reason for this restriction.
    - Make libpq ignore ENOTDIR errors when looking for an SSL client
      certificate file.
      This allows SSL connections to be established, though without a
      certificate, even when the user's home directory is set to
      something like /dev/null.
    - Fix some more field alignment issues in ecpg's SQLDA area.
    - Allow AT option in ecpg DEALLOCATE statements.
      The infrastructure to support this has been there for awhile, but
      through an oversight there was still an error check rejecting the
      case.
    - Do not use the variable name when defining a varchar structure in
      ecpg.
    - Fix "contrib/auto_explain"'s JSON output mode to produce valid JSON.
    - Fix error in "contrib/intarray"'s int[] & int[] operator.
      If the smallest integer the two input arrays have in common is 1,
      and there are smaller values in either array, then 1 would be
      incorrectly omitted from the result.
    - Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and
      decrypt_iv().
      These functions failed to report certain types of invalid-input
      errors, and would instead return random garbage values for
      incorrect input.
    - Fix one-byte buffer overrun in "contrib/test_parser".
      The code would try to read one more byte than it should, which
      would crash in corner cases. Since "contrib/test_parser" is only
      example code, this is not a security issue in itself, but bad
      example code is still bad.
    - Use __sync_lock_test_and_set() for spinlocks on ARM, if available.
      This function replaces our previous use of the SWPB instruction,
      which is deprecated and not available on ARMv6 and later. Reports
      suggest that the old code doesn't fail in an obvious way on recent
      ARM boards, but simply doesn't interlock concurrent accesses,
      leading to bizarre failures in multiprocess operation.
    - Use "-fexcess-precision=standard" option when building with gcc
      versions that accept it.
      This prevents assorted scenarios wherein recent versions of gcc
      will produce creative results.
    - Allow use of threaded Python on FreeBSD (Chris Rees)
      Our configure script previously believed that this combination
      wouldn't work; but FreeBSD fixed the problem, so remove that error
      check.
  * Drop 00git_inet_cidr_unpack.patch, 01-armel-tas.patch: Applied upstream.
  * debian/watch: Use ftp for checking, thanks Peter Eisentraut.
    (Closes: #656129)
  * debian/control: Bump Standards-Version to 3.9.3. No changes necessary.

 -- Martin Pitt <email address hidden>  Mon, 27 Feb 2012 07:30:59 +0100

Available diffs

175 of 91 results