Updates for all maintained versions of PostgreSQL are available today: 8.3.4, 8.2.10, 8.1.14, 8.0.18 and 7.4.22. These releases fix more than thirty minor issues reported and patched over the last three months. As some of these issues carry a risk of data loss, administrators of production applications should upgrade in their next possible scheduled downtime.
Additionally, this minor release also contains updates for the following timezones to support changes in local laws: Argentina, Bahamas, Brazil, Mauritius, Morocco, Pakistan, Palestine, and Paraguay. Users in these timezones should plan to upgrade as soon as possible to avoid improper calculation of daylight savings time.
Issues fixed include autovacuum crashes reported by several users, two Heap Only Tuple bugs, a foriegn key failure condition, a too-small lock address space, two Write Ahead Log bugs, several planner mistakes, and numerous "corner condition" bugs. See the release notes for more 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. As previously announced, only versions 8.2.10 and 8.3.4 of the Windows binaries are being released, as we no longer support 8.0 and 8.1 on Windows.
This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.