diff options
| author | adam <adam> | 2013-12-10 22:32:56 +0000 |
|---|---|---|
| committer | adam <adam> | 2013-12-10 22:32:56 +0000 |
| commit | 964a6b67a55204b830480c07a6b21827c5814eb3 (patch) | |
| tree | 8e0dcbfbe6ca1adfbe80050378f63bcbfb14f9f2 /databases/postgresql92/distinfo | |
| parent | 16f7e164eb001df085f70159107e3c3e280d70e5 (diff) | |
| download | pkgsrc-964a6b67a55204b830480c07a6b21827c5814eb3.tar.gz | |
The PostgreSQL Global Development Group has released a critical update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity.
The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, 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.
This release also 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.
Diffstat (limited to 'databases/postgresql92/distinfo')
| -rw-r--r-- | databases/postgresql92/distinfo | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/databases/postgresql92/distinfo b/databases/postgresql92/distinfo index a707dd15142..dad290ba02d 100644 --- a/databases/postgresql92/distinfo +++ b/databases/postgresql92/distinfo @@ -1,8 +1,8 @@ -$NetBSD: distinfo,v 1.5 2013/10/12 07:04:22 adam Exp $ +$NetBSD: distinfo,v 1.6 2013/12/10 22:32:57 adam Exp $ -SHA1 (postgresql-9.2.5.tar.bz2) = 176ac1de372c06192ec1012b17001414cfa40929 -RMD160 (postgresql-9.2.5.tar.bz2) = f156ac1770deab4d5f7bc7ed1dba1e97181a6968 -Size (postgresql-9.2.5.tar.bz2) = 16485711 bytes +SHA1 (postgresql-9.2.6.tar.bz2) = e9f124004fe6586b6d50bd14da0282d2ae613875 +RMD160 (postgresql-9.2.6.tar.bz2) = 7a74773af202730f4848ef82de333c5c18deb501 +Size (postgresql-9.2.6.tar.bz2) = 16491820 bytes SHA1 (patch-config_missing) = c2d7d742922ba6861e7660c75b7b53f09e564813 SHA1 (patch-config_perl.m4) = c7e5aaff1c47d2e33df7692a412ef984c77ffcc0 SHA1 (patch-configure) = 21b27add570cff1a24c440201eb1ed49f8223747 @@ -13,6 +13,7 @@ SHA1 (patch-src_backend_Makefile) = 76ddd3015d93b19cdd6000eaffc4f53cbd4965b5 SHA1 (patch-src_makefiles_Makefile.solaris) = 0168f5bc105ffc89d5db40907a08966d8465f5a0 SHA1 (patch-src_pl_plperl_GNUmakefile) = 2b7448d6dd8550e2ea61f40728a2780068b93d07 SHA1 (patch-src_pl_plperl_plperl.h) = bd663fa80a47f7b82ce689060750fa6e631fbc61 +SHA1 (patch-src_pl_plpython_Makefile) = d70e0cf5e20479851df3ededa50776fd04846d49 SHA1 (patch-src_timezone_localtime.c) = 622f57bc1d10f07ab73f86765cbf587eece57085 SHA1 (patch-src_timezone_private.h) = 85dac95e40efc16270885087f868aeb76e1b9214 SHA1 (patch-src_timezone_strftime.c) = 25102dce1b9b22385353af23500636fb18e3bf64 |