Quick Links

postgresql-9.2 updated to version 9.2.6-1.pgdg+1

From:	apt(dot)postgresql(dot)org repository <myon(at)debian(dot)org>
To:	PostgreSQL in Debian <pgsql-pkg-debian(at)postgresql(dot)org>
Subject:	postgresql-9.2 updated to version 9.2.6-1.pgdg+1
Date:	2013-12-05 15:08:28
Message-ID:	E1VoaXU-0005iM-EW@atalia.postgresql.org
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-pkg-debian

The package postgresql-9.2 was updated on apt.postgresql.org:

New version 9.2.6-1.pgdg+1:

Old version 9.2.5-1.pgdg+1:

Changelog:

postgresql-9.2 (9.2.6-1.pgdg+1) sid-pgdg; urgency=low

* Rebuild for sid-pgdg (jenkins-postgresql-9.2-source-
distribution=sid-37, bzr revision 403)

-- apt.postgresql.org autobuilder <myon(at)debian(dot)org> Tue, 03 Dec 2013 23:17:26 +0100

postgresql-9.2 (9.2.6-1.pgdg+1) sid-pgdg; urgency=low

* New upstream version.

+ Fix "VACUUM"'s tests to see whether it can update relfrozenxid
(Andres Freund)

In some cases "VACUUM" (either manual or autovacuum) could
incorrectly advance a table's relfrozenxid value, allowing tuples
to escape freezing, causing those rows to become invisible once
2^31 transactions have elapsed. The probability of data loss is
fairly low since multiple incorrect advancements would need to
happen before actual loss occurs, but it's not zero. In 9.2.0 and
later, the probability of loss is higher, and it's also possible to
get "could not access status of transaction" errors as a
consequence of this bug. Users upgrading from releases 9.0.4 or
8.4.8 or earlier are not affected, but all later versions contain
the bug.
The issue can be ameliorated by, after upgrading, vacuuming all
tables in all databases while having vacuum_freeze_table_age set to
zero. This will fix any latent corruption but will not be able to
fix all pre-existing data errors. However, an installation can be
presumed safe after performing this vacuuming if it has executed
fewer than 2^31 update transactions in its lifetime (check this
with SELECT txid_current() < 2^31).

+ Fix initialization of "pg_clog" and "pg_subtrans" during hot
standby startup (Andres Freund, Heikki Linnakangas)

This bug can cause data loss on standby servers at the moment they
start to accept hot-standby queries, by marking committed
transactions as uncommitted. The likelihood of such corruption is
small unless, at the time of standby startup, the primary server
has executed many updating transactions since its last checkpoint.
Symptoms include missing rows, rows that should have been deleted
being still visible, and obsolete versions of updated rows being
still visible alongside their newer versions.
This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and
9.0.14. Standby servers that have only been running earlier
releases are not at risk. It's recommended that standby servers
that have ever run any of the buggy releases be re-cloned from the
primary (e.g., with a new base backup) after upgrading.

* Refresh debian/patches/62-pg_upgrade-test-in-tmp.

-- Christoph Berg <myon(at)debian(dot)org> Tue, 03 Dec 2013 09:10:47 +0100

Browse pgsql-pkg-debian by date

	From	Date	Subject
Next Message	apt.postgresql.org repository	2013-12-05 15:08:42	postgresql-9.1 updated to version 9.1.11-1.pgdg+1
Previous Message	apt.postgresql.org repository	2013-12-05 14:48:22	postgresql-9.3 updated to version 9.3.2-1.pgdg+1