View Bazaar branches
Get this repository:
git clone https://git.launchpad.net/ubuntu/+source/postgresql-9.1
Members of Ubuntu Server Dev import team can upload to this repository. Log in for directions.

Branches

Name Last Modified Last Commit
importer/ubuntu/dsc 2018-03-16 07:18:42 UTC 2018-03-16
DSC file for 9.1.24-0ubuntu0.12.04

Author: Ubuntu Git Importer
Author Date: 2018-03-16 07:18:42 UTC

DSC file for 9.1.24-0ubuntu0.12.04

importer/ubuntu/pristine-tar 2018-03-16 07:18:24 UTC 2018-03-16
pristine-tar data for postgresql-9.1_9.1.24.orig.tar.bz2

Author: Ubuntu Git Importer
Author Date: 2018-03-16 07:18:24 UTC

pristine-tar data for postgresql-9.1_9.1.24.orig.tar.bz2

importer/debian/pristine-tar 2018-03-16 05:55:21 UTC 2018-03-16
pristine-tar data for postgresql-9.1_9.1.21.orig.tar.bz2

Author: Ubuntu Git Importer
Author Date: 2018-03-16 05:55:21 UTC

pristine-tar data for postgresql-9.1_9.1.21.orig.tar.bz2

importer/debian/dsc 2018-03-16 05:53:59 UTC 2018-03-16
DSC file for 9.1.21-0+deb7u1

Author: Ubuntu Git Importer
Author Date: 2018-03-16 05:53:59 UTC

DSC file for 9.1.21-0+deb7u1

ubuntu/precise-updates 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-prop...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: b336b9e106caf89b33d3a04268d9884c333e4939

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

applied/ubuntu/precise-devel 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precis...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: 1bd4fe6314f28cf91fe69589e26b9fb6e5222627
Unapplied parent: 5a35afb286d8916f3a23e17f754b2c15b094073c

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

applied/ubuntu/precise-proposed 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precis...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: 1bd4fe6314f28cf91fe69589e26b9fb6e5222627
Unapplied parent: 5a35afb286d8916f3a23e17f754b2c15b094073c

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

applied/ubuntu/precise-updates 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precis...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-applied version 9.1.24-0ubuntu0.12.04 to applied/ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: 1bd4fe6314f28cf91fe69589e26b9fb6e5222627
Unapplied parent: 5a35afb286d8916f3a23e17f754b2c15b094073c

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

applied/ubuntu/trusty-updates 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty...

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: cc49358095149d2ea007877f416d33d81efd76bb
Unapplied parent: 37ca90938985f3bbb3bd9fa576c62e0d6db27fb7

New changelog entries:
  * 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.

applied/ubuntu/trusty-proposed 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty...

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: cc49358095149d2ea007877f416d33d81efd76bb
Unapplied parent: 37ca90938985f3bbb3bd9fa576c62e0d6db27fb7

New changelog entries:
  * 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.

applied/ubuntu/trusty-devel 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty...

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-applied version 9.1.24-0ubuntu0.14.04 to applied/ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: cc49358095149d2ea007877f416d33d81efd76bb
Unapplied parent: 37ca90938985f3bbb3bd9fa576c62e0d6db27fb7

New changelog entries:
  * 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.

ubuntu/precise-devel 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-prop...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: b336b9e106caf89b33d3a04268d9884c333e4939

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

ubuntu/precise-proposed 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-prop...

Author: Martin Pitt
Author Date: 2016-10-27 19:33:45 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.12.04 to ubuntu/precise-proposed

Imported using git-ubuntu import.

Changelog parent: b336b9e106caf89b33d3a04268d9884c333e4939

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

ubuntu/trusty-updates 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: e668d3cd144eab103d356efa4ea26e6ef6752697

New changelog entries:
  * 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.

ubuntu/trusty-proposed 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: e668d3cd144eab103d356efa4ea26e6ef6752697

New changelog entries:
  * 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.

ubuntu/trusty-devel 2016-10-27 21:19:29 UTC 2016-10-27
Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Author: Martin Pitt
Author Date: 2016-10-27 19:26:48 UTC

Import patches-unapplied version 9.1.24-0ubuntu0.14.04 to ubuntu/trusty-proposed

Imported using git-ubuntu import.

Changelog parent: e668d3cd144eab103d356efa4ea26e6ef6752697

New changelog entries:
  * 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.

ubuntu/precise-security 2016-08-18 18:49:20 UTC 2016-08-18
Import patches-unapplied version 9.1.23-0ubuntu0.12.04 to ubuntu/precise-secu...

Author: Martin Pitt
Author Date: 2016-08-17 14:18:31 UTC

Import patches-unapplied version 9.1.23-0ubuntu0.12.04 to ubuntu/precise-security

Imported using git-ubuntu import.

Changelog parent: 88182be1f5ab3cf7957911858c6280ed1eda475a

New changelog entries:
  * 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

applied/ubuntu/trusty-security 2016-08-18 18:49:20 UTC 2016-08-18
Import patches-applied version 9.1.23-0ubuntu0.14.04 to applied/ubuntu/trusty...

Author: Martin Pitt
Author Date: 2016-08-17 14:30:41 UTC

Import patches-applied version 9.1.23-0ubuntu0.14.04 to applied/ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: df32e12a7bf3bea92937274470b162b1c2b15e83
Unapplied parent: 41ecb64dad8d12749b68de0a107c94fb67200954

New changelog entries:
  * 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.

ubuntu/trusty-security 2016-08-18 18:49:20 UTC 2016-08-18
Import patches-unapplied version 9.1.23-0ubuntu0.14.04 to ubuntu/trusty-security

Author: Martin Pitt
Author Date: 2016-08-17 14:30:41 UTC

Import patches-unapplied version 9.1.23-0ubuntu0.14.04 to ubuntu/trusty-security

Imported using git-ubuntu import.

Changelog parent: 73ffcb68cef254c2443516358e9ce2a6ac94783d

New changelog entries:
  * 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.

applied/ubuntu/precise-security 2016-08-18 18:49:20 UTC 2016-08-18
Import patches-applied version 9.1.23-0ubuntu0.12.04 to applied/ubuntu/precis...

Author: Martin Pitt
Author Date: 2016-08-17 14:18:31 UTC

Import patches-applied version 9.1.23-0ubuntu0.12.04 to applied/ubuntu/precise-security

Imported using git-ubuntu import.

Changelog parent: 3815556846ab2d010c6fc3a96156db2a3e3524ae
Unapplied parent: a44946a1a547626be690f796511217bd56a1939a

New changelog entries:
  * 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

debian/wheezy 2016-06-05 05:40:09 UTC 2016-06-05
Import patches-unapplied version 9.1.21-0+deb7u1 to debian/wheezy

Author: Christoph Berg
Author Date: 2016-04-02 12:02:53 UTC

Import patches-unapplied version 9.1.21-0+deb7u1 to debian/wheezy

Imported using git-ubuntu import.

Changelog parent: 961bfc4b32de52f4131c0aa898744b85da5494a4

New changelog entries:
  * New upstream bugfix release.
  * New upstream version.
    + 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)
    + Fix privilege escalation issue for users of PL/Java. Certain custom
      configuration settings (GUCs) for PL/Java will now be modifiable only by
      the database superuser. (CVE-2016-0766)

applied/debian/wheezy 2016-06-05 05:40:09 UTC 2016-06-05
Import patches-applied version 9.1.21-0+deb7u1 to applied/debian/wheezy

Author: Christoph Berg
Author Date: 2016-04-02 12:02:53 UTC

Import patches-applied version 9.1.21-0+deb7u1 to applied/debian/wheezy

Imported using git-ubuntu import.

Changelog parent: 19c587ce0dc8dfafd231733125a35e2f2ac56555
Unapplied parent: d0a7065b6ef4704b6d85870977efd0e838bb21f4

New changelog entries:
  * New upstream bugfix release.
  * New upstream version.
    + 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)
    + Fix privilege escalation issue for users of PL/Java. Certain custom
      configuration settings (GUCs) for PL/Java will now be modifiable only by
      the database superuser. (CVE-2016-0766)

applied/debian/jessie 2016-06-05 04:57:15 UTC 2016-06-05
Import patches-applied version 9.1.22-0+deb8u1 to applied/debian/jessie

Author: Christoph Berg
Author Date: 2016-05-27 14:03:59 UTC

Import patches-applied version 9.1.22-0+deb8u1 to applied/debian/jessie

Imported using git-ubuntu import.

Changelog parent: a821ef7f2f20b2f20037691fb1aedb1297a8210d
Unapplied parent: bb25cb712d5d68dccdc4ae9d8914b04a4840854c

New changelog entries:
  * New upstream release: No effective changes for PL/Perl, the version must
    just be higher than the one in wheezy.
  * New upstream version, relevant PL/Perl change:
    + Correctly handle empty arrays in plperl_ref_from_pg_array.

debian/jessie 2016-06-05 04:57:15 UTC 2016-06-05
Import patches-unapplied version 9.1.22-0+deb8u1 to debian/jessie

Author: Christoph Berg
Author Date: 2016-05-27 14:03:59 UTC

Import patches-unapplied version 9.1.22-0+deb8u1 to debian/jessie

Imported using git-ubuntu import.

Changelog parent: 6db9e6edfa80d65b83bef1fa45b2fb2130779093

New changelog entries:
  * New upstream release: No effective changes for PL/Perl, the version must
    just be higher than the one in wheezy.
  * New upstream version, relevant PL/Perl change:
    + Correctly handle empty arrays in plperl_ref_from_pg_array.

debian/stretch 2015-02-05 22:24:26 UTC 2015-02-05
Import patches-unapplied version 9.1.15-0+deb8u1 to debian/sid

Author: Christoph Berg
Author Date: 2015-02-05 15:58:40 UTC

Import patches-unapplied version 9.1.15-0+deb8u1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: b88d209de53f3ba72da90a19e1a0c82581dfc986

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

applied/debian/sid 2015-02-05 22:24:26 UTC 2015-02-05
Import patches-applied version 9.1.15-0+deb8u1 to applied/debian/sid

Author: Christoph Berg
Author Date: 2015-02-05 15:58:40 UTC

Import patches-applied version 9.1.15-0+deb8u1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 992b9f004aa78d0c12852c9921bbc4d2993e5d7c
Unapplied parent: dd7b411ff5b87d1276b1bd34b8afc5162d89e3b9

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

applied/debian/stretch 2015-02-05 22:24:26 UTC 2015-02-05
Import patches-applied version 9.1.15-0+deb8u1 to applied/debian/sid

Author: Christoph Berg
Author Date: 2015-02-05 15:58:40 UTC

Import patches-applied version 9.1.15-0+deb8u1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 992b9f004aa78d0c12852c9921bbc4d2993e5d7c
Unapplied parent: dd7b411ff5b87d1276b1bd34b8afc5162d89e3b9

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

debian/sid 2015-02-05 22:24:26 UTC 2015-02-05
Import patches-unapplied version 9.1.15-0+deb8u1 to debian/sid

Author: Christoph Berg
Author Date: 2015-02-05 15:58:40 UTC

Import patches-unapplied version 9.1.15-0+deb8u1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: b88d209de53f3ba72da90a19e1a0c82581dfc986

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

ubuntu/quantal-proposed 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-prop...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 1a992551f8b3de9b4fab1809569bbf3fbe139d6d

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/saucy-updates 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-...

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 55a5bacf034fbe3e431edc8869fba1d8583c741b
Unapplied parent: e99747455c6ad9ab5396c095f01e543b50fb83e0

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/quantal-updates 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quanta...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 7141dbc40922ebb2056682ea3f1de99856b47137
Unapplied parent: 5b81cfd19bdccd110b2f7b13f161b4a9a3be39e9

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

ubuntu/quantal-updates 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-prop...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 1a992551f8b3de9b4fab1809569bbf3fbe139d6d

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/quantal-proposed 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quanta...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 7141dbc40922ebb2056682ea3f1de99856b47137
Unapplied parent: 5b81cfd19bdccd110b2f7b13f161b4a9a3be39e9

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/quantal-devel 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quanta...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-applied version 9.1.13-0ubuntu0.12.10 to applied/ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 7141dbc40922ebb2056682ea3f1de99856b47137
Unapplied parent: 5b81cfd19bdccd110b2f7b13f161b4a9a3be39e9

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

ubuntu/saucy-devel 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 9442ba3204a5b496774e77c097a002649004574f

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

ubuntu/saucy-proposed 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 9442ba3204a5b496774e77c097a002649004574f

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

ubuntu/saucy-updates 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.13.10 to ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 9442ba3204a5b496774e77c097a002649004574f

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

ubuntu/quantal-devel 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-prop...

Author: Martin Pitt
Author Date: 2014-03-18 09:31:14 UTC

Import patches-unapplied version 9.1.13-0ubuntu0.12.10 to ubuntu/quantal-proposed

Imported using git-ubuntu import.

Changelog parent: 1a992551f8b3de9b4fab1809569bbf3fbe139d6d

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/saucy-devel 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-...

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 55a5bacf034fbe3e431edc8869fba1d8583c741b
Unapplied parent: e99747455c6ad9ab5396c095f01e543b50fb83e0

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/saucy-proposed 2014-03-21 18:58:27 UTC 2014-03-21
Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-...

Author: Martin Pitt
Author Date: 2014-03-18 09:26:43 UTC

Import patches-applied version 9.1.13-0ubuntu0.13.10 to applied/ubuntu/saucy-proposed

Imported using git-ubuntu import.

Changelog parent: 55a5bacf034fbe3e431edc8869fba1d8583c741b
Unapplied parent: e99747455c6ad9ab5396c095f01e543b50fb83e0

New changelog entries:
  * New upstream bug fix release. No security issues or major data loss fixes
    this time, see release.html for details. (LP: #1294006)

applied/ubuntu/trusty 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-applied version 9.1.13-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-applied version 9.1.13-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 2af308b1394140e057cfe2fd6ca1bc39cff8f00c
Unapplied parent: 018ada4b014c1b82f010e8d952e9363f29df9f93

New changelog entries:
  * 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.

applied/ubuntu/devel 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-applied version 9.1.13-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-applied version 9.1.13-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 2af308b1394140e057cfe2fd6ca1bc39cff8f00c
Unapplied parent: 018ada4b014c1b82f010e8d952e9363f29df9f93

New changelog entries:
  * 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.

applied/ubuntu/utopic 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-applied version 9.1.13-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-applied version 9.1.13-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 2af308b1394140e057cfe2fd6ca1bc39cff8f00c
Unapplied parent: 018ada4b014c1b82f010e8d952e9363f29df9f93

New changelog entries:
  * 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.

applied/ubuntu/utopic-devel 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-applied version 9.1.13-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-applied version 9.1.13-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 2af308b1394140e057cfe2fd6ca1bc39cff8f00c
Unapplied parent: 018ada4b014c1b82f010e8d952e9363f29df9f93

New changelog entries:
  * 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.

ubuntu/devel 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-unapplied version 9.1.13-1 to debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-unapplied version 9.1.13-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 84eb2e12def4a9b8eabe72f8733eb79e7d271394

New changelog entries:
  * 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.

ubuntu/trusty 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-unapplied version 9.1.13-1 to debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-unapplied version 9.1.13-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 84eb2e12def4a9b8eabe72f8733eb79e7d271394

New changelog entries:
  * 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.

ubuntu/utopic 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-unapplied version 9.1.13-1 to debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-unapplied version 9.1.13-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 84eb2e12def4a9b8eabe72f8733eb79e7d271394

New changelog entries:
  * 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.

ubuntu/utopic-devel 2014-03-20 22:22:15 UTC 2014-03-20
Import patches-unapplied version 9.1.13-1 to debian/sid

Author: Martin Pitt
Author Date: 2014-03-18 09:18:13 UTC

Import patches-unapplied version 9.1.13-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 84eb2e12def4a9b8eabe72f8733eb79e7d271394

New changelog entries:
  * 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.

applied/ubuntu/quantal-security 2014-02-24 13:23:26 UTC 2014-02-24
Import patches-applied version 9.1.12-0ubuntu0.12.10 to applied/ubuntu/quanta...

Author: Martin Pitt
Author Date: 2014-02-20 17:51:51 UTC

Import patches-applied version 9.1.12-0ubuntu0.12.10 to applied/ubuntu/quantal-security

Imported using git-ubuntu import.

Changelog parent: 62332262104fe777a5ed89a8afc5f959f8f2966b
Unapplied parent: cc3314af4e67f3a4b68e3e4346d2cf9d8ac5ed13

New changelog entries:
  * 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.

applied/ubuntu/saucy-security 2014-02-24 13:23:26 UTC 2014-02-24
Import patches-applied version 9.1.12-0ubuntu0.13.10 to applied/ubuntu/saucy-...

Author: Martin Pitt
Author Date: 2014-02-20 16:49:25 UTC

Import patches-applied version 9.1.12-0ubuntu0.13.10 to applied/ubuntu/saucy-security

Imported using git-ubuntu import.

Changelog parent: e09422fba01cd96b61e7efa2a9e95ee64814ed77
Unapplied parent: f6ab4d64ced9077df6fab086c8a5b832f7bb6d83

New changelog entries:
  * 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.

ubuntu/quantal-security 2014-02-24 13:23:26 UTC 2014-02-24
Import patches-unapplied version 9.1.12-0ubuntu0.12.10 to ubuntu/quantal-secu...

Author: Martin Pitt
Author Date: 2014-02-20 17:51:51 UTC

Import patches-unapplied version 9.1.12-0ubuntu0.12.10 to ubuntu/quantal-security

Imported using git-ubuntu import.

Changelog parent: c5d38a30a2bb94156ff186adb414a1098bd79f7e

New changelog entries:
  * 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.

ubuntu/saucy-security 2014-02-24 13:23:26 UTC 2014-02-24
Import patches-unapplied version 9.1.12-0ubuntu0.13.10 to ubuntu/saucy-security

Author: Martin Pitt
Author Date: 2014-02-20 16:49:25 UTC

Import patches-unapplied version 9.1.12-0ubuntu0.13.10 to ubuntu/saucy-security

Imported using git-ubuntu import.

Changelog parent: ec247477cc75140c4ae93bbf66b5baf9e0008704

New changelog entries:
  * 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.

applied/ubuntu/raring-updates 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring...

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: c57e7f08e99a223cc6157323c30dc0af3b23e3b3
Unapplied parent: 586ec7cfd28c4f5e76fa76a5744deecf4cd31686

New changelog entries:
  * 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.

ubuntu/raring-devel 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: 96563ea58b5e22ace25fa1ce2a88ef0f461d877e

New changelog entries:
  * 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.

ubuntu/raring-proposed 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: 96563ea58b5e22ace25fa1ce2a88ef0f461d877e

New changelog entries:
  * 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.

applied/ubuntu/raring-proposed 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring...

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: c57e7f08e99a223cc6157323c30dc0af3b23e3b3
Unapplied parent: 586ec7cfd28c4f5e76fa76a5744deecf4cd31686

New changelog entries:
  * 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.

ubuntu/raring-updates 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-unapplied version 9.1.11-0ubuntu0.13.04 to ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: 96563ea58b5e22ace25fa1ce2a88ef0f461d877e

New changelog entries:
  * 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.

applied/ubuntu/raring-devel 2013-12-06 06:13:28 UTC 2013-12-06
Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring...

Author: Martin Pitt
Author Date: 2013-12-03 09:22:12 UTC

Import patches-applied version 9.1.11-0ubuntu0.13.04 to applied/ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: c57e7f08e99a223cc6157323c30dc0af3b23e3b3
Unapplied parent: 586ec7cfd28c4f5e76fa76a5744deecf4cd31686

New changelog entries:
  * 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.

ubuntu/saucy 2013-10-10 16:16:57 UTC 2013-10-10
Import patches-unapplied version 9.1.10-1 to debian/sid

Author: Martin Pitt
Author Date: 2013-10-09 08:00:31 UTC

Import patches-unapplied version 9.1.10-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 0275bb8c1e5c7cb8268f7ad27b50e1294c9a0d9b

New changelog entries:
  * 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.

applied/ubuntu/saucy 2013-10-10 16:16:57 UTC 2013-10-10
Import patches-applied version 9.1.10-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2013-10-09 08:00:31 UTC

Import patches-applied version 9.1.10-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: c2d6354fc01bd0ad255743b4dff23a7667221619
Unapplied parent: a053d91c91c736e902e9bf6ea698e483d71f8e05

New changelog entries:
  * 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.

ubuntu/raring 2013-04-04 15:28:00 UTC 2013-04-04
Import patches-unapplied version 9.1.9-1ubuntu1 to ubuntu/raring-proposed

Author: Martin Pitt
Author Date: 2013-04-04 14:01:02 UTC

Import patches-unapplied version 9.1.9-1ubuntu1 to ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: a98d961891b2e713149ed83309eb7f221f1521a9

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

applied/ubuntu/raring 2013-04-04 15:28:00 UTC 2013-04-04
Import patches-applied version 9.1.9-1ubuntu1 to applied/ubuntu/raring-proposed

Author: Martin Pitt
Author Date: 2013-04-04 14:01:02 UTC

Import patches-applied version 9.1.9-1ubuntu1 to applied/ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: a71a11a9197f11a140c5914a88a28fbb95032da4
Unapplied parent: 709cf306ed17c0e6595121377f67b59bfe08e85d

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

ubuntu/oneiric-devel 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: d2309e0e3c7cd1592f424a6a12b87f85c4568649

New changelog entries:
  * 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.

ubuntu/oneiric-security 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: d2309e0e3c7cd1592f424a6a12b87f85c4568649

New changelog entries:
  * 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.

ubuntu/oneiric-updates 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-unapplied version 9.1.9-0ubuntu11.10 to ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: d2309e0e3c7cd1592f424a6a12b87f85c4568649

New changelog entries:
  * 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.

applied/ubuntu/oneiric-updates 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-s...

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: 68895da8db8ec64f40783d50e183ec49af2b02b8
Unapplied parent: 1a1d79f5af96911406186f32e3c92844a645ec8a

New changelog entries:
  * 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.

applied/ubuntu/oneiric-security 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-s...

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: 68895da8db8ec64f40783d50e183ec49af2b02b8
Unapplied parent: 1a1d79f5af96911406186f32e3c92844a645ec8a

New changelog entries:
  * 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.

applied/ubuntu/oneiric-devel 2013-04-04 13:33:11 UTC 2013-04-04
Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-s...

Author: Martin Pitt
Author Date: 2013-04-02 10:24:32 UTC

Import patches-applied version 9.1.9-0ubuntu11.10 to applied/ubuntu/oneiric-security

Imported using git-ubuntu import.

Changelog parent: 68895da8db8ec64f40783d50e183ec49af2b02b8
Unapplied parent: 1a1d79f5af96911406186f32e3c92844a645ec8a

New changelog entries:
  * 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.

applied/ubuntu/oneiric-proposed 2012-12-12 05:34:06 UTC 2012-12-12
Import patches-applied version 9.1.7-0ubuntu11.10 to applied/ubuntu/oneiric-p...

Author: Martin Pitt
Author Date: 2012-12-10 14:04:42 UTC

Import patches-applied version 9.1.7-0ubuntu11.10 to applied/ubuntu/oneiric-proposed

Imported using git-ubuntu import.

Changelog parent: 497391fb9fb9ec5bae4d9d16885cc2ac993c2a02
Unapplied parent: 8efabdbcbb290683eca7b447b4da91f65870136c

New changelog entries:
  * 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.

ubuntu/oneiric-proposed 2012-12-12 05:34:06 UTC 2012-12-12
Import patches-unapplied version 9.1.7-0ubuntu11.10 to ubuntu/oneiric-proposed

Author: Martin Pitt
Author Date: 2012-12-10 14:04:42 UTC

Import patches-unapplied version 9.1.7-0ubuntu11.10 to ubuntu/oneiric-proposed

Imported using git-ubuntu import.

Changelog parent: 2eae95ab6e42daf85520de355afc8a7e6cb678f6

New changelog entries:
  * 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.

applied/ubuntu/quantal 2012-09-25 10:23:54 UTC 2012-09-25
Import patches-applied version 9.1.6-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2012-09-25 03:40:23 UTC

Import patches-applied version 9.1.6-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 6f9fb4de92b43d60c71cde41af05e0bd410b3f46
Unapplied parent: 416a23dac47ad4a812bd6f0bb4ab7e22cfa879df

New changelog entries:
  * 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)

ubuntu/quantal 2012-09-25 10:23:54 UTC 2012-09-25
Import patches-unapplied version 9.1.6-1 to debian/sid

Author: Martin Pitt
Author Date: 2012-09-25 03:40:23 UTC

Import patches-unapplied version 9.1.6-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: b404f5e5ee200f4d50e8472402294e58449b7f32

New changelog entries:
  * 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)

applied/ubuntu/precise 2012-03-06 21:30:18 UTC 2012-03-06
Import patches-applied version 9.1.3-2 to applied/debian/sid

Author: Martin Pitt
Author Date: 2012-03-06 10:55:57 UTC

Import patches-applied version 9.1.3-2 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 46823064acf1433eb5a16e16ebf4859818fd8924
Unapplied parent: e3d2e036b2754a3bad9d3e28019bf3d58341efcc

New changelog entries:
  * 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)

ubuntu/precise 2012-03-06 21:30:18 UTC 2012-03-06
Import patches-unapplied version 9.1.3-2 to debian/sid

Author: Martin Pitt
Author Date: 2012-03-06 10:55:57 UTC

Import patches-unapplied version 9.1.3-2 to debian/sid

Imported using git-ubuntu import.

Changelog parent: 04a1bfa365904acc71dea36de643037e29dfb5f9

New changelog entries:
  * 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)

ubuntu/oneiric 2011-09-26 21:26:11 UTC 2011-09-26
Import patches-unapplied version 9.1.1-1 to debian/sid

Author: Martin Pitt
Author Date: 2011-09-26 12:35:36 UTC

Import patches-unapplied version 9.1.1-1 to debian/sid

Imported using git-ubuntu import.

Changelog parent: e1952cf7b0f0d7b9448476c12bce4c5f82eb932e

New changelog entries:
  * New upstream bug fix release:
    - Make pg_options_to_table return NULL for an option with no value.
      Previously such cases would result in a server crash.
    - Fix memory leak at end of a GiST index scan.
      Commands that perform many separate GiST index scans, such as
      verification of a new GiST-based exclusion constraint on a table
      already containing many rows, could transiently require large
      amounts of memory due to this leak.
    - Fix explicit reference to pg_temp schema in "CREATE TEMPORARY
      TABLE". This used to be allowed, but failed in 9.1.0.

applied/ubuntu/oneiric 2011-09-26 21:26:11 UTC 2011-09-26
Import patches-applied version 9.1.1-1 to applied/debian/sid

Author: Martin Pitt
Author Date: 2011-09-26 12:35:36 UTC

Import patches-applied version 9.1.1-1 to applied/debian/sid

Imported using git-ubuntu import.

Changelog parent: 791ca150974976bf0498b0880cc85c84b1225544
Unapplied parent: 53a1bafd879682a357f3c2a65c82fb3fc0906a9e

New changelog entries:
  * New upstream bug fix release:
    - Make pg_options_to_table return NULL for an option with no value.
      Previously such cases would result in a server crash.
    - Fix memory leak at end of a GiST index scan.
      Commands that perform many separate GiST index scans, such as
      verification of a new GiST-based exclusion constraint on a table
      already containing many rows, could transiently require large
      amounts of memory due to this leak.
    - Fix explicit reference to pg_temp schema in "CREATE TEMPORARY
      TABLE". This used to be allowed, but failed in 9.1.0.

applied/debian/experimental 2011-07-14 16:39:43 UTC 2011-07-14
Import patches-applied version 9.1~beta3-1 to applied/debian/experimental

Author: Martin Pitt
Author Date: 2011-07-14 16:39:43 UTC

Import patches-applied version 9.1~beta3-1 to applied/debian/experimental

Imported using git-ubuntu import.

Changelog parent: 351fc64cd34a6e4bc4e3f2772d93d7c5785d0c26
Unapplied parent: 18340abc2f95b0f347c4ec76ea223069f614bf90

New changelog entries:
  * New upstream beta release.
    - Works around gcc 4.6.0 bug. (Closes: #633086)
    Note that this does not change the data format since Beta 2, so no need
    to dump/reload clusters.

debian/experimental 2011-07-14 16:39:43 UTC 2011-07-14
Import patches-unapplied version 9.1~beta3-1 to debian/experimental

Author: Martin Pitt
Author Date: 2011-07-14 16:39:43 UTC

Import patches-unapplied version 9.1~beta3-1 to debian/experimental

Imported using git-ubuntu import.

Changelog parent: cf28f75dad16f05191bd91968daef47024ca7a5d

New changelog entries:
  * New upstream beta release.
    - Works around gcc 4.6.0 bug. (Closes: #633086)
    Note that this does not change the data format since Beta 2, so no need
    to dump/reload clusters.

178 of 78 results

Other repositories

Name Last Modified
lp:ubuntu/+source/postgresql-9.1 2018-03-16
11 of 1 result
You can't create new repositories for postgresql-9.1 in Ubuntu.