From d8c21181ce406b313bddfdaf49d66458942c16ed Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 9 May 2005 00:09:45 +0000 Subject: [PATCH] Update release notes for upcoming re-releases. --- doc/src/sgml/release.sgml | 56 ++++++++++++++++++++++++++++++++++----- 1 file changed, 50 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 45f39595d3..345a5b3404 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.335 2005/05/05 17:59:40 tgl Exp Release date - 2005-05-05 + 2005-05-09 @@ -72,6 +72,17 @@ misuse INTERNAL function results Guard against incorrect second parameter to record_out +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 comparisons of TIME WITH TIME ZONE values The comparison code was wrong in the case where the @@ -2684,7 +2695,7 @@ typedefs (Michael) Release date - 2005-05-05 + 2005-05-09 @@ -2795,6 +2806,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; misuse Change contrib/tsearch2 to avoid unsafe use of INTERNAL function results +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 comparisons of TIME WITH TIME ZONE values The comparison code was wrong in the case where the @@ -5236,7 +5258,7 @@ DROP SCHEMA information_schema CASCADE; Release date - 2005-05-05 + 2005-05-09 @@ -5313,6 +5335,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; Change encoding function signature to prevent misuse +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 comparisons of TIME WITH TIME ZONE values The comparison code was wrong in the case where the @@ -6511,7 +6544,7 @@ operations on bytea columns (Joe) Release date - 2005-05-05 + 2005-05-09 @@ -6531,6 +6564,17 @@ operations on bytea columns (Joe) 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 @@ -7133,7 +7177,7 @@ since PostgreSQL 7.1. Make ALTER TABLE / RENAME COLUMN update column names of indexes (Brent Verner) Fix for ALTER TABLE / ADD CONSTRAINT ... CHECK with inherited tables (Stephan Szabo) ALTER TABLE RENAME update foreign-key trigger arguments correctly (Brent Verner) -DROP AGGREGATE and COMMENT ON AGGREGATE now accepts an aggtype (Tom) +DROP AGGREGATE and COMMENT ON AGGREGATE now accept an aggtype (Tom) Add automatic return type data casting for SQL functions (Tom) Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom) Enable partial indexes (Martijn van Oosterhout) -- GitLab