[ANNOUNCE] PostgreSQL pg_upgrade bugfix 2011-04-18 release

The PostgreSQL Global Development Group today released bugfix updates
for all active branches of the PostgreSQL database system, including
versions 9.0.4, 8.4.8, 8.3.15 and 8.2.21. This update contains a
critical fix to the pg_upgrade utility which prevents significant
downtime issues. Do not use pg_upgrade without installing this update
first.

The issue with pg_upgrade and the fix are detailed on the PostgreSQL
wiki: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
Users who have already used pg_upgrade should run the database repair
script given on that page on their databases as soon as possible.

In addition to pg_upgrade, the following fixes are included in the
update. Not all fixes affect all versions.

  • fix build issues on HP-UX and Itanium
  • update time zone files for recent time zone changes
  • change SQLSTATE for Hot Standby warnings
  • prevent bgwriter hang during recovery
  • prevent recursive composite type creation
  • disallow dropping tables whose triggers are still pending
  • allow use of “replication” as a user name
  • prevent a crash during GEQO planning
  • improve join plans for tables with missing statistics
  • fix error with SELECT FOR UPDATE in a subselect
  • close PL/python array slice memory leak
  • allow SSL connections for users with no home directory
  • allow building version 9.0 with 64-bit MinGW

See the release notes for each version at
http://www.postgresql.org/docs/current/ … lease.html for a full
list of changes with details.

As with other minor releases, users are not required to dump and
reload their database in order to apply this update release; you may
simply shut down PostgreSQL and update its binaries. Users skipping
more than one update may need to check the release notes for extra,
post-update steps. Users who have previously used pg_upgrade or
pg_migrator to upgrade their databases need to run the script detailed
on the wiki page.

Download new versions now: