From 06484a87b1cc40c24e9ce907964b77daf0052024 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 7 Jun 2008 22:11:40 +0000 Subject: [PATCH] Update release notes for 8.3.3 et al. --- doc/src/sgml/release.sgml | 56 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 55 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 28a743f15d..9030d57fa1 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -63,12 +63,66 @@ do it for earlier branch release files. review, so each item is truly a community effort. + + Release 7.4.21 + + + Release date + 2008-06-12 + + + + This release contains one serious bug fix over 7.4.20. + For information about new features in the 7.4 major release, see + . + + + + Migration to Version 7.4.21 + + + A dump/restore is not required for those running 7.4.X. + However, if you are upgrading from a version earlier than 7.4.11, + see the release notes for 7.4.11. + + + + + + Changes + + + + + + Make pg_get_ruledef() parenthesize negative constants (Tom) + + + + Before this fix, a negative constant in a view or rule might be dumped + as, say, -42::integer, which is subtly incorrect: it should + be (-42)::integer due to operator precedence rules. + Usually this would make little difference, but it could interact with + another recent patch to cause + PostgreSQL to reject what had been a valid + SELECT DISTINCT view query. Since this could result in + pg_dump output failing to reload, it is being treated + as a high-priority fix. The only released versions in which dump + output is actually incorrect are 8.3.1 and 8.2.7. + + + + + + + + Release 7.4.20 Release date - 2008-06-09 + never released -- 2.39.5