ubuntu/+source/postgresql-9.1:applied/ubuntu/oneiric-proposed

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

Recent commits

b4bb144... by Martin Pitt on 2012-12-10

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.

8efabdb... by Martin Pitt on 2012-12-10

Use Debian alternatives for external tools instead of hardcoded programs

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

e303767... by Martin Pitt on 2012-12-10

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

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

404a58c... by Martin Pitt on 2012-12-10

Update tutorial README for required build dependencies.

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

3a8ad12... by Martin Pitt on 2012-12-10

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

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

c2a8b9e... by Martin Pitt on 2012-12-10

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

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

08d7d54... by Martin Pitt on 2012-12-10

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.

214cb14... by Martin Pitt on 2012-12-10

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.

497391f... by Martin Pitt on 2012-09-25

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

Imported using git-ubuntu import.

Changelog parent: da6b69899b20bcb40b93d553d13b8a5de4809f9f
Unapplied parent: bdb3d61d79ee87170454136babe14eb5d476641f

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

2eae95a... by Martin Pitt on 2012-09-25

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

Imported using git-ubuntu import.

Changelog parent: 6586ad21550d3adf5f6430edf8b95a1bdd09ed31

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