Dear professionals, PostgreSQL recommends urgently this Maintenance Releases: 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19

Received this midday by Connectikpeople from the PostgreSQL Global Development Group, the critical update to all supported versions of the PostgreSQL database system includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19.

Connectikpeople can observe that, this update fixes three serious data-loss bugs affecting replication and database maintenance. Therefore all users are urged to update

their installations at the earliest opportunity.

According to PostgreSQL, the replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. Users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists. See wiki page.

Connectikpeople has also observed that, the release fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.

Additional fixes included in this release, some of which only affect version 9.3 are available to Download or via the Release Notes.