ubuntu/+source/postgresql-9.1:applied/ubuntu/raring-devel

Last commit made on 2013-12-06
Get this branch:
git clone -b applied/ubuntu/raring-devel https://git.launchpad.net/ubuntu/+source/postgresql-9.1
Members of Ubuntu Server Dev import team can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
applied/ubuntu/raring-devel
Repository:
lp:ubuntu/+source/postgresql-9.1

Recent commits

3fd39ff... by Martin Pitt on 2013-12-03

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.

586ec7c... by Martin Pitt on 2013-12-03

Use Debian alternatives for external tools instead of hardcoded programs

Gbp-Pq: 54-debian-alternatives-for-external-tools.patch.

0b751ae... by Martin Pitt on 2013-12-03

Update pg_service.conf example to tell the Debian specific file location.

Gbp-Pq: 53-pg_service.conf_directory_doc.patch.

1d6f053... by Martin Pitt on 2013-12-03

Update tutorial README for required build dependencies.

Gbp-Pq: 52-tutorial-README.patch.

a73cd0c... by Martin Pitt on 2013-12-03

Put server Unix sockets into /var/run/postgresql/ by default

Gbp-Pq: 51-default-sockets-in-var.patch.

eb80684... by Martin Pitt on 2013-12-03

Use version specific installation directories so that several major versions can be installed in parallel.

Gbp-Pq: 50-per-version-dirs.patch.

c616c0e... by Martin Pitt on 2013-12-03

detect both python3.3 includes locations

Gbp-Pq: 03-python-includedirs.patch.

83b1424... by Martin Pitt on 2013-12-03

Relax security check on private SSL key file: The file is also considered safe if it has owner and/or group "root", and if it is group-readable (unless the group is something other than root or the database owner group).

Gbp-Pq: 02-relax-sslkey-permscheck.patch.

2f45a2c... by Martin Pitt on 2013-12-03

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.

c57e7f0... by Martin Pitt on 2013-10-09

Import patches-applied version 9.1.10-0ubuntu13.04 to applied/ubuntu/raring-proposed

Imported using git-ubuntu import.

Changelog parent: 65e9f5017238ac0fece1363d4436d23aa18f712f
Unapplied parent: aeed85ca0191ee62d08b16009d27797bd1980517

New changelog entries:
  * New upstream bug fix release (LP: #1237248). No security issues or
    critical issues this time; see HISTORY/changelog.gz for details about bug
    fixes.