diff --git a/doc/src/sgml/release-7.4.sgml b/doc/src/sgml/release-7.4.sgml
index 6131a9a4771..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 03e63202053..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 b030418d6e3..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)
diff --git a/doc/src/sgml/release-8.2.sgml b/doc/src/sgml/release-8.2.sgml
index 3f5ecec9769..f4b0056f6f8 100644
--- a/doc/src/sgml/release-8.2.sgml
+++ b/doc/src/sgml/release-8.2.sgml
@@ -1,6 +1,255 @@
-
+
+
+ Release 8.2.18
+
+
+ Release date
+ 2010-10-04
+
+
+
+ This release contains a variety of fixes from 8.2.17.
+ For information about new features in the 8.2 major release, see
+ .
+
+
+
+ Migration to Version 8.2.18
+
+
+ A dump/restore is not required for those running 8.2.X.
+ However, if you are upgrading from a version earlier than 8.2.14,
+ see the release notes for 8.2.14.
+
+
+
+
+
+ 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 Windows shared-memory allocation code
+ (Tsutomu Yamada, Magnus Hagander)
+
+
+
+ This bug led to the often-reported could not reattach to shared
+ memory
error message. This is a back-patch of a fix that was
+ applied to newer branches some time ago.
+
+
+
+
+
+ Treat exit code 128 (ERROR_WAIT_NO_CHILDREN) as non-fatal on
+ Windows (Magnus Hagander)
+
+
+
+ Under high load, Windows processes will sometimes fail at startup with
+ this error code. Formerly the postmaster treated this as a panic
+ condition and restarted the whole database, but that seems to be
+ an overreaction.
+
+
+
+
+
+ Fix possible duplicate scans of UNION ALL member relations
+ (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.
+
+
+
+
+
+ Reduce PANIC to ERROR in some occasionally-reported btree failure cases,
+ and provide additional detail in the resulting error messages
+ (Tom Lane)
+
+
+
+ This should improve the system's robustness with corrupted indexes.
+
+
+
+
+
+ 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)
+
+
+
+
+
+ Add hstore(text, text)
+ function to contrib/hstore (Robert Haas)
+
+
+
+ This function is the recommended substitute for the now-deprecated
+ => operator. It was back-patched so that future-proofed
+ code can be used with older server versions. Note that the patch will
+ be effective only after contrib/hstore is installed or
+ reinstalled in a particular database. Users might prefer to execute
+ the CREATE FUNCTION command by hand, instead.
+
+
+
+
+
+ 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.
+
+
+
+
+
+ Make Windows' N. Central Asia Standard Time timezone map to
+ Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
+
+
+
+ Microsoft changed the DST behavior of this zone in the timezone update
+ from KB976098. Asia/Novosibirsk is a better match to its new behavior.
+
+
+
+
+
+
+
+
Release 8.2.17
@@ -1661,7 +1910,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)
@@ -4883,7 +5132,7 @@
- PL/PgSQL Server-Side Language Changes
+ PL/pgSQL Server-Side Language Changes
@@ -5448,7 +5697,7 @@
linkend="guc-local-preload-libraries">local_preload_libraries
that allows libraries to be loaded into specific sessions without
explicit cooperation from the client application. This allows
- external add-ons to implement features such as a PL/PgSQL debugger.
+ external add-ons to implement features such as a PL/pgSQL debugger.
diff --git a/doc/src/sgml/release-8.3.sgml b/doc/src/sgml/release-8.3.sgml
index 95bb58ed9e8..eac868f3f15 100644
--- a/doc/src/sgml/release-8.3.sgml
+++ b/doc/src/sgml/release-8.3.sgml
@@ -1,6 +1,332 @@
-
+
+
+ Release 8.3.12
+
+
+ Release date
+ 2010-10-04
+
+
+
+ This release contains a variety of fixes from 8.3.11.
+ For information about new features in the 8.3 major release, see
+ .
+
+
+
+ Migration to Version 8.3.12
+
+
+ A dump/restore is not required for those running 8.3.X.
+ However, if you are upgrading from a version earlier than 8.3.8,
+ see the release notes for 8.3.8.
+
+
+
+
+
+ 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)
+
+
+
+
+
+ Treat exit code 128 (ERROR_WAIT_NO_CHILDREN) as non-fatal on
+ Windows (Magnus Hagander)
+
+
+
+ Under high load, Windows processes will sometimes fail at startup with
+ this error code. Formerly the postmaster treated this as a panic
+ condition and restarted the whole database, but that seems to be
+ an overreaction.
+
+
+
+
+
+ Fix incorrect usage of non-strict OR joinclauses in Append indexscans
+ (Tom Lane)
+
+
+
+ This is a back-patch of an 8.4 fix that was missed in the 8.3 branch.
+ This corrects an error introduced in 8.3.8 that could cause incorrect
+ results for outer joins when the inner relation is an inheritance tree
+ or UNION ALL subquery.
+
+
+
+
+
+ Fix possible duplicate scans of UNION ALL member relations
+ (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.
+
+
+
+
+
+ Fix failure to mark cached plans as transient (Tom Lane)
+
+
+
+ If a plan is prepared while CREATE INDEX CONCURRENTLY is
+ in progress for one of the referenced tables, it is supposed to be
+ re-planned once the index is ready for use. This was not happening
+ reliably.
+
+
+
+
+
+ Reduce PANIC to ERROR in some occasionally-reported btree failure cases,
+ and provide additional detail in the resulting error messages
+ (Tom Lane)
+
+
+
+ This should improve the system's robustness with corrupted indexes.
+
+
+
+
+
+ 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)
+
+
+
+
+
+ Improve merge join's handling of NULLs in the join columns (Tom Lane)
+
+
+
+ A merge join can now stop entirely upon reaching the first NULL,
+ if the sort order is such that NULLs sort high.
+
+
+
+
+
+ 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.
+
+
+
+
+
+ Avoid holding open old WAL segments in the walwriter process
+ (Magnus Hagander, Heikki Linnakangas)
+
+
+
+ The previous coding would prevent removal of no-longer-needed segments.
+
+
+
+
+
+ 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)
+
+
+
+
+
+ Fix REASSIGN OWNED to handle operator classes and families
+ (Asko Tiidumaa)
+
+
+
+
+
+ Fix possible core dump when comparing two empty tsquery values
+ (Tom Lane)
+
+
+
+
+
+ Fix LIKE's handling of patterns containing %
+ followed by _ (Tom Lane)
+
+
+
+ We've fixed this before, but there were still some incorrectly-handled
+ cases.
+
+
+
+
+
+ In PL/Python, defend against null pointer results from
+ PyCObject_AsVoidPtr and PyCObject_FromVoidPtr
+ (Peter Eisentraut)
+
+
+
+
+
+ Make psql recognize DISCARD ALL as a command that should
+ not be encased in a transaction block in autocommit-off mode
+ (Itagaki Takahiro)
+
+
+
+
+
+ Fix ecpg to process data from RETURNING
+ clauses correctly (Michael Meskes)
+
+
+
+
+
+ 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)
+
+
+
+
+
+ Add hstore(text, text)
+ function to contrib/hstore (Robert Haas)
+
+
+
+ This function is the recommended substitute for the now-deprecated
+ => operator. It was back-patched so that future-proofed
+ code can be used with older server versions. Note that the patch will
+ be effective only after contrib/hstore is installed or
+ reinstalled in a particular database. Users might prefer to execute
+ the CREATE FUNCTION command by hand, instead.
+
+
+
+
+
+ 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.
+
+
+
+
+
+ Make Windows' N. Central Asia Standard Time timezone map to
+ Asia/Novosibirsk, not Asia/Almaty (Magnus Hagander)
+
+
+
+ Microsoft changed the DST behavior of this zone in the timezone update
+ from KB976098. Asia/Novosibirsk is a better match to its new behavior.
+
+
+
+
+
+
+
+
Release 8.3.11
@@ -2239,7 +2565,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)
@@ -3914,7 +4240,7 @@ current_date < 2017-11-17
- Previously PL/PgSQL functions that referenced temporary tables
+ Previously PL/pgSQL functions that referenced temporary tables
would fail if the temporary table was dropped and recreated
between function invocations, unless EXECUTE was
used. This improvement fixes that problem and many related issues.
@@ -4740,7 +5066,7 @@ current_date < 2017-11-17
The first request for statistics in a transaction takes a statistics
snapshot that does not change during the transaction. This function
allows the snapshot to be discarded and a new snapshot loaded during
- the next statistics query. This is particularly useful for PL/PgSQL
+ the next statistics query. This is particularly useful for PL/pgSQL
functions, which are confined to a single transaction.
@@ -4835,7 +5161,7 @@ current_date < 2017-11-17
- PL/PgSQL Server-Side Language
+ PL/pgSQL Server-Side Language
@@ -4848,7 +5174,7 @@ current_date < 2017-11-17
Allow IN as an alternative to
- FROM in PL/PgSQL's FETCH
+ FROM in PL/pgSQL's FETCH
statement, for consistency with the backend's
FETCH command (Pavel Stehule)
@@ -4856,7 +5182,7 @@ current_date < 2017-11-17
- Add MOVE to PL/PgSQL (Magnus, Pavel Stehule,
+ Add MOVE to PL/pgSQL (Magnus, Pavel Stehule,
Neil)
@@ -4867,7 +5193,7 @@ current_date < 2017-11-17
- This adds convenient syntax for PL/PgSQL set-returning functions
+ This adds convenient syntax for PL/pgSQL set-returning functions
that want to return the result of a query. RETURN QUERY
is easier and more efficient than a loop
around RETURN NEXT.