This bug was fixed in the package postgresql-9.1 - 9.1.6-0ubuntu12.04
---------------
postgresql-9.1 (9.1.6-0ubuntu12.04) precise-proposed; urgency=low
* New upstream bug fix release: (LP: #1055944)
- Fix persistence marking of shared buffers during WAL replay.
This mistake can result in buffers not being written out during
checkpoints, resulting in data corruption if the server later
crashes without ever having written those buffers. Corruption can
occur on any server following crash recovery, but it is
significantly more likely to occur on standby slave servers since
those perform much more WAL replay. There is a low probability of
corruption of btree and GIN indexes. There is a much higher
probability of corruption of table "visibility maps". Fortunately,
visibility maps are non-critical data in 9.1, so the worst
consequence of such corruption in 9.1 installations is transient
inefficiency of vacuuming. Table data proper cannot be corrupted by
this bug.
While no index corruption due to this bug is known to have occurred
in the field, as a precautionary measure it is recommended that
production installations "REINDEX" all btree and GIN indexes at a
convenient time after upgrading to 9.1.6.
Also, if you intend to do an in-place upgrade to 9.2.X, before
doing so it is recommended to perform a "VACUUM" of all tables
while having vacuum_freeze_table_age set to zero. This will ensure
that any lingering wrong data in the visibility maps is corrected
before 9.2.X can depend on it. vacuum_cost_delay can be adjusted to
reduce the performance impact of vacuuming, while causing it to
take longer to finish.
- See HISTORY/changelog.gz for the other bug fixes.
-- Martin Pitt <[email protected]> Tue, 25 Sep 2012 07:21:13 +0200
** Changed in: postgresql-9.1 (Ubuntu Precise)
Status: Fix Committed => Fix Released
** Changed in: postgresql-9.1 (Ubuntu Oneiric)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1055944
Title:
New bug fix releases: 9.1.6, 8.4.14, 8.3.21
Status in “postgresql-8.3” package in Ubuntu:
Fix Released
Status in “postgresql-8.4” package in Ubuntu:
Invalid
Status in “postgresql-9.1” package in Ubuntu:
Fix Released
Status in “postgresql-8.4” source package in Lucid:
Fix Released
Status in “postgresql-8.4” source package in Natty:
Fix Released
Status in “postgresql-9.1” source package in Oneiric:
Fix Released
Status in “postgresql-9.1” source package in Precise:
Fix Released
Bug description:
PostgreSQL announced new microreleases yesterday:
http://www.postgresql.org/about/news/1416/
-9.1 includes a rather serious data loss fix and thus should get into
stables as soon as possible. -8.4 is less urgent, but still has a
number of nice bug fixes. PostgreSQL has a standing SRU microrelease
exception.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1055944/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
