ubuntu/+source/postgresql-9.1:applied/ubuntu/quantal

Last commit made on 2012-09-25
Get this branch:
git clone -b applied/ubuntu/quantal 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/quantal
Repository:
lp:ubuntu/+source/postgresql-9.1

Recent commits

e861163... by Martin Pitt on 2012-09-25

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)

416a23d... by Martin Pitt on 2012-09-25

Use Debian alternatives for external tools instead of hardcoded programs

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

a0da5ed... by Martin Pitt on 2012-09-25

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

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

9b60ad8... by Martin Pitt on 2012-09-25

Update tutorial README for required build dependencies.

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

32970f6... by Martin Pitt on 2012-09-25

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

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

14383a4... by Martin Pitt on 2012-09-25

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

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

85e0664... by Martin Pitt on 2012-09-25

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.

77a0950... by Martin Pitt on 2012-09-25

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)

6f9fb4d... by Martin Pitt on 2012-08-31

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

Imported using git-ubuntu import.

Changelog parent: 5a0812cbffb10abc1cc3eec778bd521961a9688b
Unapplied parent: ea1493d3e95bd2e51d4c2ff4659f5c39b91ba5b7

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

b404f5e... by Martin Pitt on 2012-08-31

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

Imported using git-ubuntu import.

Changelog parent: a44fbcdbe74eef418b36220922101b7532cf815f

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