Release date
- 2005-05-05
+ 2005-05-09
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
Release date
- 2005-05-05
+ 2005-05-09
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
Release date
- 2005-05-05
+ 2005-05-09
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
Release date
- 2005-05-05
+ 2005-05-09
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.
+
TIME WITH TIME ZONE> values
Additional buffer overrun checks in plpgsql
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)