PostgreSQL 8.3.4, 8.2.10 等更新版本发布
PostgreSQL数据库所有维护版本的更新今天发布：8.3.4, 8.2.10, 8.1.14, 8.0.18 和7.4.22。这些版本修复了过去三个月报告和修补的30多个小问题。至于其中的一些问题带来的数据丢失风险，负责产品应用的数据库管理员应该在其下一个可能的预定停机时间升级。此外，该小版本发布还包括有以下时区的更新，以支持局部法则的变化：阿根廷，巴哈马，巴西，毛里求斯，摩洛哥，巴基斯坦，巴勒斯坦，和巴拉圭。在这些时区的用户应该尽快计划升级，以避免不正确夏时令的计算。
修正的自动问题包括几个用户报告的自动数据库清理事故，两个堆只有元组的bug，一个外键失败条件，过小的锁地址空间，两个写前log错误，有几个策划的错误，和众多的“隅角条件”bug。更多的细节见的release notes 。
与其他小版本的发布一样，用户不需要转存和重新导入他们的数据库来应用此更新版本，你可以简单地关闭PostgreSQL数据库并更新其二进制文件。如果用户跳过一个以上的更新可能需要先查看的发行说明，在去更新。正如先前所宣布的，只有Windows的8.2.10和8.3.4版本二进制文件被发布，因为我们不再支持Windows的8.0和8.1。
原发布说明如下：
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.
[*]Release Notes
[*]Source Code
[*]Binaries
页:
[1]