From: Tom Lane Date: Mon, 9 May 2005 00:10:53 +0000 (+0000) Subject: Update release notes for upcoming re-releases. X-Git-Tag: REL7_2_8 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6a36111ecaf0fd435267f4d46fffcea714d87627;p=thirdparty%2Fpostgresql.git Update release notes for upcoming re-releases. --- diff --git a/HISTORY b/HISTORY index 1a8baf228ff..8468859d9f4 100644 --- a/HISTORY +++ b/HISTORY @@ -3,7 +3,7 @@ Release 7.2.8 - Release date: 2005-05-05 + Release date: 2005-05-09 This release contains a variety of fixes from 7.2.7, including one security-related issue. @@ -16,6 +16,16 @@ Changes + * Repair ancient race condition that allowed a transaction to be + seen as committed for some purposes (eg SELECT FOR UPDATE) + slightly sooner than for other purposes + This is an extremely serious bug since it could lead to apparent + data inconsistencies being briefly visible to applications. + * Repair race condition between relation extension and VACUUM + This could theoretically have caused loss of a page's worth of + freshly-inserted data, although the scenario seems of very low + probability. There are no known cases of it having caused more + than an Assert failure. * Fix EXTRACT(EPOCH) for TIME WITH TIME ZONE values * Additional buffer overrun checks in plpgsql (Neil) * Fix pg_dump to dump index names and trigger names containing % diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 43b46a6f285..e6e68629558 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -10,7 +10,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.12 2005/05/05 20:10: Release date - 2005-05-05 + 2005-05-09 @@ -30,6 +30,17 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.12 2005/05/05 20:10: Changes +Repair ancient race condition that allowed a transaction to be +seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner +than for other purposes +This is an extremely serious bug since it could lead to apparent +data inconsistencies being briefly visible to applications. +Repair race condition between relation extension and +VACUUM +This could theoretically have caused loss of a page's worth of +freshly-inserted data, although the scenario seems of very low probability. +There are no known cases of it having caused more than an Assert failure. + Fix EXTRACT(EPOCH) for TIME WITH TIME ZONE values Additional buffer overrun checks in plpgsql