PostgreSQL 2011-12-05 Cumulative Bug-Fix Release

Posted on 2011-12-05 by PostgreSQL Global Development Group

The PostgreSQL Global Development Group today released updates for all active branches of the PostgreSQL object-relational database system, including versions 9.1.2, 9.0.6, 8.4.10, 8.3.17 and 8.2.23. Users of any of the several affected features in this release, including binary replication, should update their PostgreSQL installations as soon as possible.

This is also the last update for PostgreSQL 8.2, which is now End-Of-Life (EOL). Users of version 8.2 should plan to upgrade their PostgreSQL installations to 8.3 or later within the next couple of months. For more information, see our Release Support Policy.

The features affected by this update include: binary replication and hot standby, GIN indexes, the citext extension, pg_upgrade, window function aggregate sorting, self-referential foreign keys, PL/perl, and general Extension handling. Users of these features should apply the updates right away.

This release contains 52 fixes to version 9.1, and a smaller number of fixes to older versions, including:

  • Fix bugs in information_schema.referential_constraints view**
  • Correct collations for citext columns and indexes**
  • Prevent possible crash when joining to a scalar function
  • Prevent transitory data corruption of GIN indexes after a crash
  • Prevent data corruption on TOAST columns when copying data
  • Fix failures during hot standby startup
  • Correct another "variable not found in subplan target list" bug
  • Fix bug with sorting on aggregate expressions in windowing functions
  • Multiple bug fixes for pg_upgrade
  • Change Foreign Key creation order to better support self-referential keys**
  • Multiple bug fixes to CREATE EXTENSION
  • Ensure that function return type and data returned from PL/perl agree
  • Ensure that PL/perl strings are always UTF-8
  • Assorted bug fixes for various Extensions
  • Updates to the time zone database, particularly to CST6

Changes marked with ** above require additional, post-update steps in order to fix all described issues. See the release notes for each version for a full list of changes with details of the fixes and steps.

As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Perform post-update steps after the database is restarted.

Download new versions now: