+ This release contains a variety of fixes from 8.3.16.
+ A dump/restore is not required for those running 8.3.X.
+ definition as explained in the first changelog item below.
+ see the release notes for 8.3.8.
+ depends on a different constraint than the one it really does.
+ to be fixed.
+ corrupt results in certain corner cases.
+ paths that could trigger the same bug.
+ toast table would always belong to a system catalog.
+ datum as per usual convention.
+ not be re-read.
+ Don't let
+ linkend="guc-transform-null-equals">transform_null_equals
+ affect CASE foo WHEN NULL ... constructs
+ (Heikki Linnakangas)
+
+
+ transform_null_equals is only supposed to affect
+ foo = NULL expressions written directly by the user, not
+ equality checks generated internally by this form of CASE.
+
+
+
+
+ Change foreign-key trigger creation order to better support
+ self-referential foreign keys (Tom Lane)
+
+
+ For a cascading foreign key that references its own table, a row update
+ will fire both the ON UPDATE trigger and the
+ CHECK trigger as one event. The ON UPDATE
+ trigger must execute first, else the CHECK will check a
+ non-final state of the row and possibly throw an inappropriate error.
+ However, the firing order of these triggers is determined by their
+ names, which generally sort in creation order since the triggers have
+ auto-generated names following the convention
+ RI_ConstraintTrigger_NNNN. A proper fix would require
+ modifying that convention, which we will do in 9.2, but it seems risky
+ to change it in existing releases. So this patch just changes the
+ creation order of the triggers. Users encountering this type of error
+ should drop and re-create the foreign key constraint to get its
+ triggers into the right order.
+
+
+
+
+ Avoid floating-point underflow while tracking buffer allocation rate
+ (Greg Matthews)
+
+
+ While harmless in itself, on certain platforms this would result in
+ annoying kernel log messages.
+
+
+
+
+ Preserve blank lines within commands in
psql's command+ history (Robert Haas)
+
+
+ The former behavior could cause problems if an empty line was removed
+ from within a string literal, for example.
+
+
+
+
+ Fix
pg_dump to dump user-defined casts between+ auto-generated types, such as table rowtypes (Tom Lane)
+
+
+
+
+ Use the preferred version of
xsubpp to build PL/Perl,+ not necessarily the operating system's main copy
+ (David Wheeler and Alex Hunsaker)
+
+
+
+
+ Fix incorrect coding in contrib/dict_int and
+ contrib/dict_xsyn (Tom Lane)
+
+
+ Some functions incorrectly assumed that memory returned by
+ palloc() is guaranteed zeroed.
+
+
+
+
+ Honor query cancel interrupts promptly in pgstatindex()
+ (Robert Haas)
+
+
+
+
+ Ensure VPATH builds properly install all server header files
+ (Peter Eisentraut)
+
+
+
+
+ Shorten file names reported in verbose error messages (Peter Eisentraut)
+
+
+ Regular builds have always reported just the name of the C file
+ containing the error message call, but VPATH builds formerly
+ reported an absolute path name.
+
+
+
+
+ Fix interpretation of Windows timezone names for Central America
+ (Tom Lane)
+
+
+ Map Central America Standard Time to CST6, not
+ CST6CDT, because DST is generally not observed anywhere in
+ Central America.
+
+
+
+
+ Update time zone data files to
tzdata release 2011n+ for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
+ also historical corrections for Alaska and British East Africa.
+
+
+
+
+
+
+
+
Release 8.3.16
+
+
Release 8.4.10
+
+
+
Release Date
+ 2011-12-05
+
+
+ This release contains a variety of fixes from 8.4.9.
+ For information about new features in the 8.4 major release, see
+ .
+
+
+
+
Migration to Version 8.4.10
+
+ A dump/restore is not required for those running 8.4.X.
+
+
+ However, a longstanding error was discovered in the definition of the
+ information_schema.referential_constraints view. If you
+ rely on correct results from that view, you should replace its
+ definition as explained in the first changelog item below.
+
+
+ Also, if you are upgrading from a version earlier than 8.4.8,
+ see the release notes for 8.4.8.
+
+
+
+
+
+
Changes
+
+
+
+
+ Fix bugs in information_schema.referential_constraints view
+ (Tom Lane)
+
+
+ This view was being insufficiently careful about matching the
+ foreign-key constraint to the depended-on primary or unique key
+ constraint. That could result in failure to show a foreign key
+ constraint at all, or showing it multiple times, or claiming that it
+ depends on a different constraint than the one it really does.
+
+
+ Since the view definition is installed by
initdb,+ merely upgrading will not fix the problem. If you need to fix this
+ in an existing installation, you can (as a superuser) drop the
+ information_schema schema then re-create it by sourcing
+ SHAREDIR/information_schema.sql.
+ (Run pg_config --sharedir if you're uncertain where
+ SHAREDIR is.) This must be repeated in each database
+ to be fixed.
+
+
+
+
+ Fix incorrect replay of WAL records for GIN index updates
+ (Tom Lane)
+
+
+ This could result in transiently failing to find index entries after
+ a crash, or on a hot-standby server. The problem would be repaired
+ by the next VACUUM of the index, however.
+
+
+
+
+ Fix TOAST-related data corruption during CREATE TABLE dest AS
+ SELECT * FROM src or INSERT INTO dest SELECT * FROM src
+ (Tom Lane)
+
+
+ If a table has been modified by ALTER TABLE ADD COLUMN,
+ attempts to copy its data verbatim to another table could produce
+ corrupt results in certain corner cases.
+ The problem can only manifest in this precise form in 8.4 and later,
+ but we patched earlier versions as well in case there are other code
+ paths that could trigger the same bug.
+
+
+
+
+ Fix race condition during toast table access from stale syscache entries
+ (Tom Lane)
+
+
+ The typical symptom was transient errors like missing chunk
+ number 0 for toast value NNNNN in pg_toast_2619, where the cited
+ toast table would always belong to a system catalog.
+
+
+
+
+ Track dependencies of functions on items used in parameter default
+ expressions (Tom Lane)
+
+
+ Previously, a referenced object could be dropped without having dropped
+ or modified the function, leading to misbehavior when the function was
+ used. Note that merely installing this update will not fix the missing
+ dependency entries; to do that, you'd need to CREATE OR
+ REPLACE each such function afterwards. If you have functions whose
+ defaults depend on non-built-in objects, doing so is recommended.
+
+
+
+
+ Allow inlining of set-returning SQL functions with multiple OUT
+ parameters (Tom Lane)
+
+
+
+
+ Make DatumGetInetP() unpack inet datums that have a 1-byte
+ header, and add a new macro, DatumGetInetPP(), that does
+ not (Heikki Linnakangas)
+
+
+ This change affects no core code, but might prevent crashes in add-on
+ code that expects DatumGetInetP() to produce an unpacked
+ datum as per usual convention.
+
+
+
+
+ Improve locale support in money type's input and output
+ (Tom Lane)
+
+
+ Aside from not supporting all standard
+ lc_monetary
+ formatting options, the input and output functions were inconsistent,
+ meaning there were locales in which dumped money values could
+ not be re-read.
+
+
+
+
+ Don't let
+ linkend="guc-transform-null-equals">transform_null_equals
+ affect CASE foo WHEN NULL ... constructs
+ (Heikki Linnakangas)
+
+
+ transform_null_equals is only supposed to affect
+ foo = NULL expressions written directly by the user, not
+ equality checks generated internally by this form of CASE.
+
+
+
+
+ Change foreign-key trigger creation order to better support
+ self-referential foreign keys (Tom Lane)
+
+
+ For a cascading foreign key that references its own table, a row update
+ will fire both the ON UPDATE trigger and the
+ CHECK trigger as one event. The ON UPDATE
+ trigger must execute first, else the CHECK will check a
+ non-final state of the row and possibly throw an inappropriate error.
+ However, the firing order of these triggers is determined by their
+ names, which generally sort in creation order since the triggers have
+ auto-generated names following the convention
+ RI_ConstraintTrigger_NNNN. A proper fix would require
+ modifying that convention, which we will do in 9.2, but it seems risky
+ to change it in existing releases. So this patch just changes the
+ creation order of the triggers. Users encountering this type of error
+ should drop and re-create the foreign key constraint to get its
+ triggers into the right order.
+
+
+
+
+ Avoid floating-point underflow while tracking buffer allocation rate
+ (Greg Matthews)
+
+
+ While harmless in itself, on certain platforms this would result in
+ annoying kernel log messages.
+
+
+
+
+ Preserve configuration file name and line number values when starting
+ child processes under Windows (Tom Lane)
+
+
+ Formerly, these would not be displayed correctly in the
+ pg_settings view.
+
+
+
+
+ Preserve blank lines within commands in
psql's command+ history (Robert Haas)
+
+
+ The former behavior could cause problems if an empty line was removed
+ from within a string literal, for example.
+
+
+
+
+ Fix
pg_dump to dump user-defined casts between+ auto-generated types, such as table rowtypes (Tom Lane)
+
+
+
+
+ Use the preferred version of
xsubpp to build PL/Perl,+ not necessarily the operating system's main copy
+ (David Wheeler and Alex Hunsaker)
+
+
+
+
+ Fix incorrect coding in contrib/dict_int and
+ contrib/dict_xsyn (Tom Lane)
+
+
+ Some functions incorrectly assumed that memory returned by
+ palloc() is guaranteed zeroed.
+
+
+
+
+ Honor query cancel interrupts promptly in pgstatindex()
+ (Robert Haas)
+
+
+
+
+ Ensure VPATH builds properly install all server header files
+ (Peter Eisentraut)
+
+
+
+
+ Shorten file names reported in verbose error messages (Peter Eisentraut)
+
+
+ Regular builds have always reported just the name of the C file
+ containing the error message call, but VPATH builds formerly
+ reported an absolute path name.
+
+
+
+
+ Fix interpretation of Windows timezone names for Central America
+ (Tom Lane)
+
+
+ Map Central America Standard Time to CST6, not
+ CST6CDT, because DST is generally not observed anywhere in
+ Central America.
+
+
+
+
+ Update time zone data files to
tzdata release 2011n+ for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
+ also historical corrections for Alaska and British East Africa.
+
+
+
+
+
+
+
+
Release 8.4.9
+
+
Release 9.0.6
+
+
+
Release Date
+ 2011-12-05
+
+
+ This release contains a variety of fixes from 9.0.5.
+ For information about new features in the 9.0 major release, see
+ .
+
+
+
+
Migration to Version 9.0.6
+
+ A dump/restore is not required for those running 9.0.X.
+
+
+ However, a longstanding error was discovered in the definition of the
+ information_schema.referential_constraints view. If you
+ rely on correct results from that view, you should replace its
+ definition as explained in the first changelog item below.
+
+
+ Also, if you are upgrading from a version earlier than 9.0.4,
+ see the release notes for 9.0.4.
+
+
+
+
+
+
Changes
+
+
+
+
+ Fix bugs in information_schema.referential_constraints view
+ (Tom Lane)
+
+
+ This view was being insufficiently careful about matching the
+ foreign-key constraint to the depended-on primary or unique key
+ constraint. That could result in failure to show a foreign key
+ constraint at all, or showing it multiple times, or claiming that it
+ depends on a different constraint than the one it really does.
+
+
+ Since the view definition is installed by
initdb,+ merely upgrading will not fix the problem. If you need to fix this
+ in an existing installation, you can (as a superuser) drop the
+ information_schema schema then re-create it by sourcing
+ SHAREDIR/information_schema.sql.
+ (Run pg_config --sharedir if you're uncertain where
+ SHAREDIR is.) This must be repeated in each database
+ to be fixed.
+
+
+
+
+ Fix possible crash during UPDATE or DELETE that
+ joins to the output of a scalar-returning function (Tom Lane)
+
+
+ A crash could only occur if the target row had been concurrently
+ updated, so this problem surfaced only intermittently.
+
+
+
+
+ Fix incorrect replay of WAL records for GIN index updates
+ (Tom Lane)
+
+
+ This could result in transiently failing to find index entries after
+ a crash, or on a hot-standby server. The problem would be repaired
+ by the next VACUUM of the index, however.
+
+
+
+
+ Fix TOAST-related data corruption during CREATE TABLE dest AS
+ SELECT * FROM src or INSERT INTO dest SELECT * FROM src
+ (Tom Lane)
+
+
+ If a table has been modified by ALTER TABLE ADD COLUMN,
+ attempts to copy its data verbatim to another table could produce
+ corrupt results in certain corner cases.
+ The problem can only manifest in this precise form in 8.4 and later,
+ but we patched earlier versions as well in case there are other code
+ paths that could trigger the same bug.
+
+
+
+
+ Fix possible failures during hot standby startup (Simon Riggs)
+
+
+
+
+ Start hot standby faster when initial snapshot is incomplete
+ (Simon Riggs)
+
+
+
+
+ Fix race condition during toast table access from stale syscache entries
+ (Tom Lane)
+
+
+ The typical symptom was transient errors like missing chunk
+ number 0 for toast value NNNNN in pg_toast_2619, where the cited
+ toast table would always belong to a system catalog.
+
+
+
+
+ Track dependencies of functions on items used in parameter default
+ expressions (Tom Lane)
+
+
+ Previously, a referenced object could be dropped without having dropped
+ or modified the function, leading to misbehavior when the function was
+ used. Note that merely installing this update will not fix the missing
+ dependency entries; to do that, you'd need to CREATE OR
+ REPLACE each such function afterwards. If you have functions whose
+ defaults depend on non-built-in objects, doing so is recommended.
+
+
+
+
+ Allow inlining of set-returning SQL functions with multiple OUT
+ parameters (Tom Lane)
+
+
+
+
+ Don't trust deferred-unique indexes for join removal (Tom Lane and Marti
+ Raudsepp)
+
+
+ A deferred uniqueness constraint might not hold intra-transaction,
+ so assuming that it does could give incorrect query results.
+
+
+
+
+ Make DatumGetInetP() unpack inet datums that have a 1-byte
+ header, and add a new macro, DatumGetInetPP(), that does
+ not (Heikki Linnakangas)
+
+
+ This change affects no core code, but might prevent crashes in add-on
+ code that expects DatumGetInetP() to produce an unpacked
+ datum as per usual convention.
+
+
+
+
+ Improve locale support in money type's input and output
+ (Tom Lane)
+
+
+ Aside from not supporting all standard
+ lc_monetary
+ formatting options, the input and output functions were inconsistent,
+ meaning there were locales in which dumped money values could
+ not be re-read.
+
+
+
+
+ Don't let
+ linkend="guc-transform-null-equals">transform_null_equals
+ affect CASE foo WHEN NULL ... constructs
+ (Heikki Linnakangas)
+
+
+ transform_null_equals is only supposed to affect
+ foo = NULL expressions written directly by the user, not
+ equality checks generated internally by this form of CASE.
+
+
+
+
+ Change foreign-key trigger creation order to better support
+ self-referential foreign keys (Tom Lane)
+
+
+ For a cascading foreign key that references its own table, a row update
+ will fire both the ON UPDATE trigger and the
+ CHECK trigger as one event. The ON UPDATE
+ trigger must execute first, else the CHECK will check a
+ non-final state of the row and possibly throw an inappropriate error.
+ However, the firing order of these triggers is determined by their
+ names, which generally sort in creation order since the triggers have
+ auto-generated names following the convention
+ RI_ConstraintTrigger_NNNN. A proper fix would require
+ modifying that convention, which we will do in 9.2, but it seems risky
+ to change it in existing releases. So this patch just changes the
+ creation order of the triggers. Users encountering this type of error
+ should drop and re-create the foreign key constraint to get its
+ triggers into the right order.
+
+
+
+
+ Avoid floating-point underflow while tracking buffer allocation rate
+ (Greg Matthews)
+
+
+ While harmless in itself, on certain platforms this would result in
+ annoying kernel log messages.
+
+
+
+
+ Preserve configuration file name and line number values when starting
+ child processes under Windows (Tom Lane)
+
+
+ Formerly, these would not be displayed correctly in the
+ pg_settings view.
+
+
+
+
+ Fix incorrect field alignment in
ecpg's SQLDA area+ (Zoltan Boszormenyi)
+
+
+
+
+ Preserve blank lines within commands in
psql's command+ history (Robert Haas)
+
+
+ The former behavior could cause problems if an empty line was removed
+ from within a string literal, for example.
+
+
+
+
+ Fix
pg_dump to dump user-defined casts between+ auto-generated types, such as table rowtypes (Tom Lane)
+
+
+
+
+ Assorted fixes for
pg_upgrade (Bruce Momjian)+
+
+ Handle exclusion constraints correctly, avoid failures on Windows,
+ don't complain about mismatched toast table names in 8.4 databases.
+
+
+
+
+ Use the preferred version of
xsubpp to build PL/Perl,+ not necessarily the operating system's main copy
+ (David Wheeler and Alex Hunsaker)
+
+
+
+
+ Fix incorrect coding in contrib/dict_int and
+ contrib/dict_xsyn (Tom Lane)
+
+
+ Some functions incorrectly assumed that memory returned by
+ palloc() is guaranteed zeroed.
+
+
+
+
+ Fix assorted errors in contrib/unaccent's configuration
+ file parsing (Tom Lane)
+
+
+
+
+ Honor query cancel interrupts promptly in pgstatindex()
+ (Robert Haas)
+
+
+
+
+ Fix incorrect quoting of log file name in Mac OS X start script
+ (Sidar Lopez)
+
+
+
+
+ Ensure VPATH builds properly install all server header files
+ (Peter Eisentraut)
+
+
+
+
+ Shorten file names reported in verbose error messages (Peter Eisentraut)
+
+
+ Regular builds have always reported just the name of the C file
+ containing the error message call, but VPATH builds formerly
+ reported an absolute path name.
+
+
+
+
+ Fix interpretation of Windows timezone names for Central America
+ (Tom Lane)
+
+
+ Map Central America Standard Time to CST6, not
+ CST6CDT, because DST is generally not observed anywhere in
+ Central America.
+
+
+
+
+ Update time zone data files to
tzdata release 2011n+ for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
+ also historical corrections for Alaska and British East Africa.
+
+
+
+
+
+
+
+
Release 9.0.5
projects / postgresql.git / commitdiff