diff --git a/doc/src/sgml/release-7.4.sgml b/doc/src/sgml/release-7.4.sgml
index 837e781b0a8..2c52be70064 100644
--- a/doc/src/sgml/release-7.4.sgml
+++ b/doc/src/sgml/release-7.4.sgml
@@ -1,6 +1,103 @@
-
+
+
+ Release 7.4.30
+
+
+ Release date
+ 2010-10-04
+
+
+
+ This release contains a variety of fixes from 7.4.29.
+ For information about new features in the 7.4 major release, see
+ .
+
+
+
+ This is expected to be the last PostgreSQL release
+ in the 7.4.X series. Users are encouraged to update to a newer
+ release branch soon.
+
+
+
+ Migration to Version 7.4.30
+
+
+ A dump/restore is not required for those running 7.4.X.
+ However, if you are upgrading from a version earlier than 7.4.26,
+ see the release notes for 7.4.26.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Prevent possible crashes in pg_get_expr() by disallowing
+ it from being called with an argument that is not one of the system
+ catalog columns it's intended to be used with
+ (Heikki Linnakangas, Tom Lane)
+
+
+
+
+
+ Fix cannot handle unplanned sub-select
error (Tom Lane)
+
+
+
+ This occurred when a sub-select contains a join alias reference that
+ expands into an expression containing another sub-select.
+
+
+
+
+
+ Take care to fsync the contents of lockfiles (both
+ postmaster.pid and the socket lockfile) while writing them
+ (Tom Lane)
+
+
+
+ This omission could result in corrupted lockfile contents if the
+ machine crashes shortly after postmaster start. That could in turn
+ prevent subsequent attempts to start the postmaster from succeeding,
+ until the lockfile is manually removed.
+
+
+
+
+
+ Improve contrib/dblink's handling of tables containing
+ dropped columns (Tom Lane)
+
+
+
+
+
+ Fix connection leak after duplicate connection name
+ errors in contrib/dblink (Itagaki Takahiro)
+
+
+
+
+
+ Update build infrastructure and documentation to reflect the source code
+ repository's move from CVS to Git (Magnus Hagander and others)
+
+
+
+
+
+
+
+
Release 7.4.29
@@ -1897,7 +1994,7 @@ enabled
files during postmaster startup
Various memory leakage fixes
Various portability improvements
-Fix PL/PgSQL to handle var := var correctly when
+Fix PL/pgSQL to handle var := var correctly when
the variable is of pass-by-reference type
Update contrib/tsearch2 to use current Snowball
code
diff --git a/doc/src/sgml/release-8.0.sgml b/doc/src/sgml/release-8.0.sgml
index 6a662d5083a..ae2b3c04cf7 100644
--- a/doc/src/sgml/release-8.0.sgml
+++ b/doc/src/sgml/release-8.0.sgml
@@ -1,6 +1,173 @@
-
+
+
+ Release 8.0.26
+
+
+ Release date
+ 2010-10-04
+
+
+
+ This release contains a variety of fixes from 8.0.25.
+ For information about new features in the 8.0 major release, see
+ .
+
+
+
+ This is expected to be the last PostgreSQL release
+ in the 8.0.X series. Users are encouraged to update to a newer
+ release branch soon.
+
+
+
+ Migration to Version 8.0.26
+
+
+ A dump/restore is not required for those running 8.0.X.
+ However, if you are upgrading from a version earlier than 8.0.22,
+ see the release notes for 8.0.22.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Prevent possible crashes in pg_get_expr() by disallowing
+ it from being called with an argument that is not one of the system
+ catalog columns it's intended to be used with
+ (Heikki Linnakangas, Tom Lane)
+
+
+
+
+
+ Fix cannot handle unplanned sub-select
error (Tom Lane)
+
+
+
+ This occurred when a sub-select contains a join alias reference that
+ expands into an expression containing another sub-select.
+
+
+
+
+
+ Defend against functions returning setof record where not all the
+ returned rows are actually of the same rowtype (Tom Lane)
+
+
+
+
+
+ Take care to fsync the contents of lockfiles (both
+ postmaster.pid and the socket lockfile) while writing them
+ (Tom Lane)
+
+
+
+ This omission could result in corrupted lockfile contents if the
+ machine crashes shortly after postmaster start. That could in turn
+ prevent subsequent attempts to start the postmaster from succeeding,
+ until the lockfile is manually removed.
+
+
+
+
+
+ Avoid recursion while assigning XIDs to heavily-nested
+ subtransactions (Andres Freund, Robert Haas)
+
+
+
+ The original coding could result in a crash if there was limited
+ stack space.
+
+
+
+
+
+ Fix log_line_prefix's %i escape,
+ which could produce junk early in backend startup (Tom Lane)
+
+
+
+
+
+ Fix possible data corruption in ALTER TABLE ... SET
+ TABLESPACE when archiving is enabled (Jeff Davis)
+
+
+
+
+
+ Allow CREATE DATABASE and ALTER DATABASE ... SET
+ TABLESPACE to be interrupted by query-cancel (Guillaume Lelarge)
+
+
+
+
+
+ In PL/Python, defend against null pointer results from
+ PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
+ (Peter Eisentraut)
+
+
+
+
+
+ Improve contrib/dblink's handling of tables containing
+ dropped columns (Tom Lane)
+
+
+
+
+
+ Fix connection leak after duplicate connection name
+ errors in contrib/dblink (Itagaki Takahiro)
+
+
+
+
+
+ Fix contrib/dblink to handle connection names longer than
+ 62 bytes correctly (Itagaki Takahiro)
+
+
+
+
+
+ Update build infrastructure and documentation to reflect the source code
+ repository's move from CVS to Git (Magnus Hagander and others)
+
+
+
+
+
+ Update time zone data files to tzdata release 2010l
+ for DST law changes in Egypt and Palestine; also historical corrections
+ for Finland.
+
+
+
+ This change also adds new names for two Micronesian timezones:
+ Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
+ abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
+ Pacific/Ponape.
+
+
+
+
+
+
+
+
Release 8.0.25
@@ -2512,7 +2679,7 @@ when opening the file fails
constraints more reliably
Fix password prompting in pg_restore on
Windows
-Fix PL/PgSQL to handle var := var correctly when
+Fix PL/pgSQL to handle var := var correctly when
the variable is of pass-by-reference type
Fix PL/Perl %_SHARED so it's actually
shared
diff --git a/doc/src/sgml/release-8.1.sgml b/doc/src/sgml/release-8.1.sgml
index cd520abd76b..37e3751c0e1 100644
--- a/doc/src/sgml/release-8.1.sgml
+++ b/doc/src/sgml/release-8.1.sgml
@@ -1,6 +1,187 @@
-
+
+
+ Release 8.1.22
+
+
+ Release date
+ 2010-10-04
+
+
+
+ This release contains a variety of fixes from 8.1.21.
+ For information about new features in the 8.1 major release, see
+ .
+
+
+
+ The PostgreSQL community will stop releasing updates
+ for the 8.1.X release series in November 2010.
+ Users are encouraged to update to a newer release branch soon.
+
+
+
+ Migration to Version 8.1.22
+
+
+ A dump/restore is not required for those running 8.1.X.
+ However, if you are upgrading from a version earlier than 8.1.18,
+ see the release notes for 8.1.18.
+
+
+
+
+
+ Changes
+
+
+
+
+
+ Prevent possible crashes in pg_get_expr() by disallowing
+ it from being called with an argument that is not one of the system
+ catalog columns it's intended to be used with
+ (Heikki Linnakangas, Tom Lane)
+
+
+
+
+
+ Fix cannot handle unplanned sub-select
error (Tom Lane)
+
+
+
+ This occurred when a sub-select contains a join alias reference that
+ expands into an expression containing another sub-select.
+
+
+
+
+
+ Prevent show_session_authorization() from crashing within autovacuum
+ processes (Tom Lane)
+
+
+
+
+
+ Defend against functions returning setof record where not all the
+ returned rows are actually of the same rowtype (Tom Lane)
+
+
+
+
+
+ Fix possible failure when hashing a pass-by-reference function result
+ (Tao Ma, Tom Lane)
+
+
+
+
+
+ Take care to fsync the contents of lockfiles (both
+ postmaster.pid and the socket lockfile) while writing them
+ (Tom Lane)
+
+
+
+ This omission could result in corrupted lockfile contents if the
+ machine crashes shortly after postmaster start. That could in turn
+ prevent subsequent attempts to start the postmaster from succeeding,
+ until the lockfile is manually removed.
+
+
+
+
+
+ Avoid recursion while assigning XIDs to heavily-nested
+ subtransactions (Andres Freund, Robert Haas)
+
+
+
+ The original coding could result in a crash if there was limited
+ stack space.
+
+
+
+
+
+ Fix log_line_prefix's %i escape,
+ which could produce junk early in backend startup (Tom Lane)
+
+
+
+
+
+ Fix possible data corruption in ALTER TABLE ... SET
+ TABLESPACE when archiving is enabled (Jeff Davis)
+
+
+
+
+
+ Allow CREATE DATABASE and ALTER DATABASE ... SET
+ TABLESPACE to be interrupted by query-cancel (Guillaume Lelarge)
+
+
+
+
+
+ In PL/Python, defend against null pointer results from
+ PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
+ (Peter Eisentraut)
+
+
+
+
+
+ Improve contrib/dblink's handling of tables containing
+ dropped columns (Tom Lane)
+
+
+
+
+
+ Fix connection leak after duplicate connection name
+ errors in contrib/dblink (Itagaki Takahiro)
+
+
+
+
+
+ Fix contrib/dblink to handle connection names longer than
+ 62 bytes correctly (Itagaki Takahiro)
+
+
+
+
+
+ Update build infrastructure and documentation to reflect the source code
+ repository's move from CVS to Git (Magnus Hagander and others)
+
+
+
+
+
+ Update time zone data files to tzdata release 2010l
+ for DST law changes in Egypt and Palestine; also historical corrections
+ for Finland.
+
+
+
+ This change also adds new names for two Micronesian timezones:
+ Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred
+ abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over
+ Pacific/Ponape.
+
+
+
+
+
+
+
+
Release 8.1.21
@@ -1212,7 +1393,7 @@
- Fix PL/PgSQL to not fail when a FOR loop's target variable
+ Fix PL/pgSQL to not fail when a FOR loop's target variable
is a record containing composite-type fields (Tom)
@@ -4040,9 +4221,9 @@ psql -t -f fixseq.sql db1 | psql -e db1
Previously, only a predefined list of time zone names were
supported by AT TIME ZONE. Now any supported time
zone name can be used, e.g.:
-
- SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
-
+
+SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
+
In the above query, the time zone used is adjusted based on the
daylight saving time rules that were in effect on the supplied
date.
@@ -4116,10 +4297,10 @@ psql -t -f fixseq.sql db1 | psql -e db1
the next day even if a daylight saving time adjustment occurs
between, whereas adding 24 hours will give a different
local time when this happens. For example, under US DST rules:
-
- '2005-04-03 00:00:00-05' + '1 day' = '2005-04-04 00:00:00-04'
- '2005-04-03 00:00:00-05' + '24 hours' = '2005-04-04 01:00:00-04'
-
+
+'2005-04-03 00:00:00-05' + '1 day' = '2005-04-04 00:00:00-04'
+'2005-04-03 00:00:00-05' + '24 hours' = '2005-04-04 01:00:00-04'
+
@@ -4343,7 +4524,7 @@ psql -t -f fixseq.sql db1 | psql -e db1
- Allow SQL and PL/PgSQL functions to use OUT and
+ Allow SQL and PL/pgSQL functions to use OUT and
INOUT parameters (Tom)
@@ -4378,12 +4559,12 @@ psql -t -f fixseq.sql db1 | psql -e db1
- PL/PgSQL Server-Side Language Changes
+ PL/pgSQL Server-Side Language Changes
- Overhaul the memory management of PL/PgSQL functions (Neil)
+ Overhaul the memory management of PL/pgSQL functions (Neil)
The parsetree of each function is now stored in a separate
@@ -4426,7 +4607,7 @@ psql -t -f fixseq.sql db1 | psql -e db1
Add support for an optional INTO clause to
- PL/PgSQL's EXECUTE statement (Pavel Stehule, Neil)
+ PL/pgSQL's EXECUTE statement (Pavel Stehule, Neil)