From: Tom Lane Date: Wed, 4 Jun 2008 03:16:23 +0000 (+0000) Subject: Draft release notes for upcoming back-branch updates. X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=2b88353893ee838c91e2bc122f1a90bad491d0df;p=users%2Fbernd%2Fpostgres.git Draft release notes for upcoming back-branch updates. --- diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 533a87f02a..979f7151e8 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -63,6 +63,201 @@ do it for earlier branch release files. review, so each item is truly a community effort. + + Release 8.2.8 + + + Release date + 2008-06-09 + + + + This release contains a variety of fixes from 8.2.7. + For information about new features in the 8.2 major release, see + . + + + + Migration to Version 8.2.8 + + + A dump/restore is not required for those running 8.2.X. + However, if you are upgrading from a version earlier than 8.2.7, + see the release notes for 8.2.7. + + + + + + Changes + + + + + + Fix ERRORDATA_STACK_SIZE exceeded crash that + occurred on Windows when using UTF-8 database encoding and a different + client encoding (Tom) + + + + + + Fix ALTER TABLE ADD COLUMN ... PRIMARY KEY so that the new + column is correctly checked to see if it's been initialized to all + non-nulls (Brendan Jurd) + + + + Previous versions neglected to check this requirement at all. + + + + + + Fix possible CREATE TABLE failure when inheriting the + same constraint from multiple parent relations that + inherited that constraint from a common ancestor (Tom) + + + + + + Fix pg_get_ruledef() to show the alias, if any, attached + to the target table of an UPDATE or DELETE + (Tom) + + + + + + Fix GIN bug that could result in a too many LWLocks + taken failure (Teodor) + + + + + + Avoid possible crash when decompressing corrupted data + (Zdenek Kotala) + + + + + + Repair two places where SIGTERM exit of a backend could leave corrupted + state in shared memory (Tom) + + + + Neither case is very important if SIGTERM is used to shut down the + whole database cluster together, but there was a problem if someone + tried to SIGTERM individual backends. + + + + + + Fix conversions between ISO-8859-5 and other encodings to handle + Cyrillic Yo characters (e and E with + two dots) (Sergey Burladyan) + + + + + + Fix several datatype input functions, notably array_in(), + that were allowing unused bytes in their results to contain + uninitialized, unpredictable values (Tom) + + + + This could lead to failures in which two apparently identical literal + values were not seen as equal, resulting in the parser complaining + about unmatched ORDER BY and DISTINCT + expressions. + + + + + + Fix a corner case in regular-expression substring matching + (substring(string from + pattern)) (Tom) + + + + The problem occurs when there is a match to the pattern overall but + the user has specified a parenthesized subexpression and that + subexpression hasn't got a match. An example is + substring('foo' from 'foo(bar)?'). + This should return NULL, since (bar) isn't matched, but + it was mistakenly returning the whole-pattern match instead (ie, + foo). + + + + + + Update time zone data files to tzdata release 2008c (for + DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, and + Argentina/San_Luis) + + + + + + Fix incorrect result from ecpg's + PGTYPEStimestamp_sub() function (Michael) + + + + + + Fix broken GiST comparison function for contrib/tsearch2's + tsquery type (Teodor) + + + + + + Fix possible crashes in contrib/cube functions (Tom) + + + + + + Fix core dump in contrib/xml2's + xpath_table() function when the input query returns a + NULL value (Tom) + + + + + + Fix contrib/xml2's makefile to not override + CFLAGS (Tom) + + + + + + Fix DatumGetBool macro to not fail with gcc + 4.3 (Tom) + + + + This problem affects old style (V0) C functions that + return boolean. The fix is already in 8.3, but the need to + back-patch it was not realized at the time. + + + + + + + + Release 8.2.7 @@ -147,7 +342,7 @@ do it for earlier branch release files. - This was formerly allowed but trying to do it had various unpleasant + This was formerly allowed but trying to do it had various unpleasant consequences, notably that the originating backend could not exit as long as an UNLISTEN remained uncommitted. @@ -323,7 +518,7 @@ do it for earlier branch release files. This failure has only been observed to occur when a user-defined datatype's output routine issues a NOTICE, but there is no - guaranteee it couldn't happen due to other causes. + guarantee it couldn't happen due to other causes. @@ -3841,32 +4036,22 @@ do it for earlier branch release files. - - Release 8.1.11 + + Release 8.1.12 Release date - 2008-01-07 + 2008-06-09 - This release contains a variety of fixes from 8.1.10, - including fixes for significant security issues. + This release contains a variety of fixes from 8.1.11. For information about new features in the 8.1 major release, see . - - This is the last 8.1.X release for which the PostgreSQL - community will produce binary packages for Windows. - Windows users are encouraged to move to 8.2.X or later, - since there are Windows-specific fixes in 8.2.X that - are impractical to back-port. 8.1.X will continue to - be supported on other platforms. - - - Migration to Version 8.1.11 + Migration to Version 8.1.12 A dump/restore is not required for those running 8.1.X. @@ -3883,192 +4068,452 @@ do it for earlier branch release files. - Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + Fix ALTER TABLE ADD COLUMN ... PRIMARY KEY so that the new + column is correctly checked to see if it's been initialized to all + non-nulls (Brendan Jurd) - Functions used in index expressions and partial-index - predicates are evaluated whenever a new table entry is made. It has - long been understood that this poses a risk of trojan-horse code - execution if one modifies a table owned by an untrustworthy user. - (Note that triggers, defaults, check constraints, etc. pose the - same type of risk.) But functions in indexes pose extra danger - because they will be executed by routine maintenance operations - such as VACUUM FULL, which are commonly performed - automatically under a superuser account. For example, a nefarious user - can execute code with superuser privileges by setting up a - trojan-horse index definition and waiting for the next routine vacuum. - The fix arranges for standard maintenance operations - (including VACUUM, ANALYZE, REINDEX, - and CLUSTER) to execute as the table owner rather than - the calling user, using the same privilege-switching mechanism already - used for SECURITY DEFINER functions. To prevent bypassing - this security measure, execution of SET SESSION - AUTHORIZATION and SET ROLE is now forbidden within a - SECURITY DEFINER context. (CVE-2007-6600) + Previous versions neglected to check this requirement at all. - Repair assorted bugs in the regular-expression package (Tom, Will Drewry) + Fix possible CREATE TABLE failure when inheriting the + same constraint from multiple parent relations that + inherited that constraint from a common ancestor (Tom) + + - Suitably crafted regular-expression patterns could cause crashes, - infinite or near-infinite looping, and/or massive memory consumption, - all of which pose denial-of-service hazards for applications that - accept regex search patterns from untrustworthy sources. - (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067) + Fix conversions between ISO-8859-5 and other encodings to handle + Cyrillic Yo characters (e and E with + two dots) (Sergey Burladyan) - Require non-superusers who use /contrib/dblink to use only - password authentication, as a security measure (Joe) + Fix a few datatype input functions + that were allowing unused bytes in their results to contain + uninitialized, unpredictable values (Tom) - The fix that appeared for this in 8.1.10 was incomplete, as it plugged - the hole for only some dblink functions. (CVE-2007-6601, - CVE-2007-3278) + This could lead to failures in which two apparently identical literal + values were not seen as equal, resulting in the parser complaining + about unmatched ORDER BY and DISTINCT + expressions. - Update time zone data files to tzdata release 2007k - (in particular, recent Argentina changes) (Tom) + Fix a corner case in regular-expression substring matching + (substring(string from + pattern)) (Tom) - - - Improve planner's handling of LIKE/regex estimation in non-C locales - (Tom) + The problem occurs when there is a match to the pattern overall but + the user has specified a parenthesized subexpression and that + subexpression hasn't got a match. An example is + substring('foo' from 'foo(bar)?'). + This should return NULL, since (bar) isn't matched, but + it was mistakenly returning the whole-pattern match instead (ie, + foo). - Fix planner failure in some cases of WHERE false AND var IN - (SELECT ...) (Tom) + Update time zone data files to tzdata release 2008c (for + DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, + Argentina/San_Luis, and Chile) - Preserve the tablespace of indexes that are - rebuilt by ALTER TABLE ... ALTER COLUMN TYPE (Tom) + Fix incorrect result from ecpg's + PGTYPEStimestamp_sub() function (Michael) - Make archive recovery always start a new WAL timeline, rather than only - when a recovery stop time was used (Simon) - - - - This avoids a corner-case risk of trying to overwrite an existing - archived copy of the last WAL segment, and seems simpler and cleaner - than the original definition. + Fix core dump in contrib/xml2's + xpath_table() function when the input query returns a + NULL value (Tom) - Make VACUUM not use all of maintenance_work_mem - when the table is too small for it to be useful (Alvaro) + Fix contrib/xml2's makefile to not override + CFLAGS (Tom) - Fix potential crash in translate() when using a multibyte - database encoding (Tom) + Fix DatumGetBool macro to not fail with gcc + 4.3 (Tom) - - - Fix overflow in extract(epoch from interval) for intervals - exceeding 68 years (Tom) + This problem affects old style (V0) C functions that + return boolean. The fix is already in 8.3, but the need to + back-patch it was not realized at the time. - Fix PL/Perl to not fail when a UTF-8 regular expression is used - in a trusted function (Andrew) + Fix longstanding LISTEN/NOTIFY + race condition (Tom) - - - Fix PL/Perl to cope when platform's Perl defines type bool - as int rather than char (Tom) + In rare cases a session that had just executed a + LISTEN might not get a notification, even though + one would be expected because the concurrent transaction executing + NOTIFY was observed to commit later. - While this could theoretically happen anywhere, no standard build of - Perl did things this way ... until Mac OS X 10.5. + A side effect of the fix is that a transaction that has executed + a not-yet-committed LISTEN command will not see any + row in pg_listener for the LISTEN, + should it choose to look; formerly it would have. This behavior + was never documented one way or the other, but it is possible that + some applications depend on the old behavior. - Fix PL/Python to not crash on long exception messages (Alvaro) + Disallow LISTEN and UNLISTEN within a + prepared transaction (Tom) - - - Fix pg_dump to correctly handle inheritance child tables - that have default expressions different from their parent's (Tom) + This was formerly allowed but trying to do it had various unpleasant + consequences, notably that the originating backend could not exit + as long as an UNLISTEN remained uncommitted. - Fix libpq crash when PGPASSFILE refers - to a file that is not a plain file (Martin Pitt) + Fix rare crash when an error occurs during a query using a hash index + (Heikki) - ecpg parser fixes (Michael) + Fix input of datetime values for February 29 in years BC (Tom) - - - Make contrib/pgcrypto defend against - OpenSSL libraries that fail on keys longer than 128 - bits; which is the case at least on some Solaris versions (Marko Kreen) + The former coding was mistaken about which years were leap years. - Make contrib/tablefunc's crosstab() handle - NULL rowid as a category in its own right, rather than crashing (Joe) + Fix unrecognized node type error in some variants of + ALTER OWNER (Tom) - Fix tsvector and tsquery output routines to - escape backslashes correctly (Teodor, Bruce) + Fix pg_ctl to correctly extract the postmaster's port + number from command-line options (Itagaki Takahiro, Tom) - - - Fix crash of to_tsvector() on huge input strings (Teodor) + Previously, pg_ctl start -w could try to contact the + postmaster on the wrong port, leading to bogus reports of startup + failure. + + + + + + Use + + + This is known to be necessary when building PostgreSQL + with gcc 4.3 or later. + + + + + + Fix display of constant expressions in ORDER BY + and GROUP BY (Tom) + + + + An explictly casted constant would be shown incorrectly. This could + for example lead to corruption of a view definition during + dump and reload. + + + + + + Fix libpq to handle NOTICE messages correctly + during COPY OUT (Tom) + + + + This failure has only been observed to occur when a user-defined + datatype's output routine issues a NOTICE, but there is no + guarantee it couldn't happen due to other causes. + + + + + + + + + + Release 8.1.11 + + + Release date + 2008-01-07 + + + + This release contains a variety of fixes from 8.1.10, + including fixes for significant security issues. + For information about new features in the 8.1 major release, see + . + + + + This is the last 8.1.X release for which the PostgreSQL + community will produce binary packages for Windows. + Windows users are encouraged to move to 8.2.X or later, + since there are Windows-specific fixes in 8.2.X that + are impractical to back-port. 8.1.X will continue to + be supported on other platforms. + + + + Migration to Version 8.1.11 + + + A dump/restore is not required for those running 8.1.X. + However, if you are upgrading from a version earlier than 8.1.2, + see the release notes for 8.1.2. + + + + + + Changes + + + + + + Prevent functions in indexes from executing with the privileges of + the user running VACUUM, ANALYZE, etc (Tom) + + + + Functions used in index expressions and partial-index + predicates are evaluated whenever a new table entry is made. It has + long been understood that this poses a risk of trojan-horse code + execution if one modifies a table owned by an untrustworthy user. + (Note that triggers, defaults, check constraints, etc. pose the + same type of risk.) But functions in indexes pose extra danger + because they will be executed by routine maintenance operations + such as VACUUM FULL, which are commonly performed + automatically under a superuser account. For example, a nefarious user + can execute code with superuser privileges by setting up a + trojan-horse index definition and waiting for the next routine vacuum. + The fix arranges for standard maintenance operations + (including VACUUM, ANALYZE, REINDEX, + and CLUSTER) to execute as the table owner rather than + the calling user, using the same privilege-switching mechanism already + used for SECURITY DEFINER functions. To prevent bypassing + this security measure, execution of SET SESSION + AUTHORIZATION and SET ROLE is now forbidden within a + SECURITY DEFINER context. (CVE-2007-6600) + + + + + + Repair assorted bugs in the regular-expression package (Tom, Will Drewry) + + + + Suitably crafted regular-expression patterns could cause crashes, + infinite or near-infinite looping, and/or massive memory consumption, + all of which pose denial-of-service hazards for applications that + accept regex search patterns from untrustworthy sources. + (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067) + + + + + + Require non-superusers who use /contrib/dblink to use only + password authentication, as a security measure (Joe) + + + + The fix that appeared for this in 8.1.10 was incomplete, as it plugged + the hole for only some dblink functions. (CVE-2007-6601, + CVE-2007-3278) + + + + + + Update time zone data files to tzdata release 2007k + (in particular, recent Argentina changes) (Tom) + + + + + + Improve planner's handling of LIKE/regex estimation in non-C locales + (Tom) + + + + + + Fix planner failure in some cases of WHERE false AND var IN + (SELECT ...) (Tom) + + + + + + Preserve the tablespace of indexes that are + rebuilt by ALTER TABLE ... ALTER COLUMN TYPE (Tom) + + + + + + Make archive recovery always start a new WAL timeline, rather than only + when a recovery stop time was used (Simon) + + + + This avoids a corner-case risk of trying to overwrite an existing + archived copy of the last WAL segment, and seems simpler and cleaner + than the original definition. + + + + + + Make VACUUM not use all of maintenance_work_mem + when the table is too small for it to be useful (Alvaro) + + + + + + Fix potential crash in translate() when using a multibyte + database encoding (Tom) + + + + + + Fix overflow in extract(epoch from interval) for intervals + exceeding 68 years (Tom) + + + + + + Fix PL/Perl to not fail when a UTF-8 regular expression is used + in a trusted function (Andrew) + + + + + + Fix PL/Perl to cope when platform's Perl defines type bool + as int rather than char (Tom) + + + + While this could theoretically happen anywhere, no standard build of + Perl did things this way ... until Mac OS X 10.5. + + + + + + Fix PL/Python to not crash on long exception messages (Alvaro) + + + + + + Fix pg_dump to correctly handle inheritance child tables + that have default expressions different from their parent's (Tom) + + + + + + Fix libpq crash when PGPASSFILE refers + to a file that is not a plain file (Martin Pitt) + + + + + + ecpg parser fixes (Michael) + + + + + + Make contrib/pgcrypto defend against + OpenSSL libraries that fail on keys longer than 128 + bits; which is the case at least on some Solaris versions (Marko Kreen) + + + + + + Make contrib/tablefunc's crosstab() handle + NULL rowid as a category in its own right, rather than crashing (Joe) + + + + + + Fix tsvector and tsquery output routines to + escape backslashes correctly (Teodor, Bruce) + + + + + + Fix crash of to_tsvector() on huge input strings (Teodor) @@ -7183,88 +7628,325 @@ psql -t -f fixseq.sql db1 | psql -e db1 - - - Move /contrib/findoidjoins to - /src/tools (Tom) - - + + + Move /contrib/findoidjoins to + /src/tools (Tom) + + + + + + Remove the <<, >>, + &<, and &> operators from + /contrib/cube + + + These operators were not useful. + + + + + + Improve /contrib/btree_gist (Janko Richter) + + + + + + Improve /contrib/pgbench (Tomoaki Sato, Tatsuo) + + + There is now a facility for testing with SQL command scripts given + by the user, instead of only a hard-wired command sequence. + + + + + + Improve /contrib/pgcrypto (Marko Kreen) + + + + + + + Implementation of OpenPGP symmetric-key and public-key encryption + + + Both RSA and Elgamal public-key algorithms are supported. + + + + + + Stand alone build: include SHA256/384/512 hashes, Fortuna PRNG + + + + + + OpenSSL build: support 3DES, use internal AES with OpenSSL < 0.9.7 + + + + + + Take build parameters (OpenSSL, zlib) from configure result + + + There is no need to edit the Makefile anymore. + + + + + + Remove support for libmhash and libmcrypt + + + + + + + + + + + + + + Release 8.0.16 + + + Release date + 2008-06-09 + + + + This release contains a variety of fixes from 8.0.15. + For information about new features in the 8.0 major release, see + . + + + + Migration to Version 8.0.16 + + + A dump/restore is not required for those running 8.0.X. + However, if you are upgrading from a version earlier than 8.0.6, + see the release notes for 8.0.6. + + + + + + Changes + + + + + + Fix ALTER TABLE ADD COLUMN ... PRIMARY KEY so that the new + column is correctly checked to see if it's been initialized to all + non-nulls (Brendan Jurd) + + + + Previous versions neglected to check this requirement at all. + + + + + + Fix possible CREATE TABLE failure when inheriting the + same constraint from multiple parent relations that + inherited that constraint from a common ancestor (Tom) + + + + + + Fix conversions between ISO-8859-5 and other encodings to handle + Cyrillic Yo characters (e and E with + two dots) (Sergey Burladyan) + + + + + + Fix a few datatype input functions + that were allowing unused bytes in their results to contain + uninitialized, unpredictable values (Tom) + + + + This could lead to failures in which two apparently identical literal + values were not seen as equal, resulting in the parser complaining + about unmatched ORDER BY and DISTINCT + expressions. + + + + + + Fix a corner case in regular-expression substring matching + (substring(string from + pattern)) (Tom) + + + + The problem occurs when there is a match to the pattern overall but + the user has specified a parenthesized subexpression and that + subexpression hasn't got a match. An example is + substring('foo' from 'foo(bar)?'). + This should return NULL, since (bar) isn't matched, but + it was mistakenly returning the whole-pattern match instead (ie, + foo). + + + + + + Update time zone data files to tzdata release 2008c (for + DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, + Argentina/San_Luis, and Chile) + + + + + + Fix incorrect result from ecpg's + PGTYPEStimestamp_sub() function (Michael) + + + + + + Fix core dump in contrib/xml2's + xpath_table() function when the input query returns a + NULL value (Tom) + + + + + + Fix contrib/xml2's makefile to not override + CFLAGS (Tom) + + + + + + Fix DatumGetBool macro to not fail with gcc + 4.3 (Tom) + + + + This problem affects old style (V0) C functions that + return boolean. The fix is already in 8.3, but the need to + back-patch it was not realized at the time. + + + + + + Fix longstanding LISTEN/NOTIFY + race condition (Tom) + + + + In rare cases a session that had just executed a + LISTEN might not get a notification, even though + one would be expected because the concurrent transaction executing + NOTIFY was observed to commit later. + + + + A side effect of the fix is that a transaction that has executed + a not-yet-committed LISTEN command will not see any + row in pg_listener for the LISTEN, + should it choose to look; formerly it would have. This behavior + was never documented one way or the other, but it is possible that + some applications depend on the old behavior. + + - - - Remove the <<, >>, - &<, and &> operators from - /contrib/cube - - - These operators were not useful. - - + + + Fix rare crash when an error occurs during a query using a hash index + (Heikki) + + - - - Improve /contrib/btree_gist (Janko Richter) - - + + + Fix input of datetime values for February 29 in years BC (Tom) + - - - Improve /contrib/pgbench (Tomoaki Sato, Tatsuo) - - - There is now a facility for testing with SQL command scripts given - by the user, instead of only a hard-wired command sequence. - - + + The former coding was mistaken about which years were leap years. + + - - - Improve /contrib/pgcrypto (Marko Kreen) - + + + Fix unrecognized node type error in some variants of + ALTER OWNER (Tom) + + - + + + Fix pg_ctl to correctly extract the postmaster's port + number from command-line options (Itagaki Takahiro, Tom) + - - - Implementation of OpenPGP symmetric-key and public-key encryption - - - Both RSA and Elgamal public-key algorithms are supported. - - + + Previously, pg_ctl start -w could try to contact the + postmaster on the wrong port, leading to bogus reports of startup + failure. + + - - - Stand alone build: include SHA256/384/512 hashes, Fortuna PRNG - - + + + Use - - - OpenSSL build: support 3DES, use internal AES with OpenSSL < 0.9.7 - - + + This is known to be necessary when building PostgreSQL + with gcc 4.3 or later. + + - - - Take build parameters (OpenSSL, zlib) from configure result - - - There is no need to edit the Makefile anymore. - - + + + Fix display of constant expressions in ORDER BY + and GROUP BY (Tom) + - - - Remove support for libmhash and libmcrypt - - + + An explictly casted constant would be shown incorrectly. This could + for example lead to corruption of a view definition during + dump and reload. + + - - + + + Fix libpq to handle NOTICE messages correctly + during COPY OUT (Tom) + - - + + This failure has only been observed to occur when a user-defined + datatype's output routine issues a NOTICE, but there is no + guarantee it couldn't happen due to other causes. + + + + @@ -11126,6 +11808,151 @@ typedefs (Michael) + + Release 7.4.20 + + + Release date + 2008-06-09 + + + + This release contains a variety of fixes from 7.4.19. + For information about new features in the 7.4 major release, see + . + + + + Migration to Version 7.4.20 + + + 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 + + + + + + Fix conversions between ISO-8859-5 and other encodings to handle + Cyrillic Yo characters (e and E with + two dots) (Sergey Burladyan) + + + + + + Fix a few datatype input functions + that were allowing unused bytes in their results to contain + uninitialized, unpredictable values (Tom) + + + + This could lead to failures in which two apparently identical literal + values were not seen as equal, resulting in the parser complaining + about unmatched ORDER BY and DISTINCT + expressions. + + + + + + Fix a corner case in regular-expression substring matching + (substring(string from + pattern)) (Tom) + + + + The problem occurs when there is a match to the pattern overall but + the user has specified a parenthesized subexpression and that + subexpression hasn't got a match. An example is + substring('foo' from 'foo(bar)?'). + This should return NULL, since (bar) isn't matched, but + it was mistakenly returning the whole-pattern match instead (ie, + foo). + + + + + + Fix incorrect result from ecpg's + PGTYPEStimestamp_sub() function (Michael) + + + + + + Fix DatumGetBool macro to not fail with gcc + 4.3 (Tom) + + + + This problem affects old style (V0) C functions that + return boolean. The fix is already in 8.3, but the need to + back-patch it was not realized at the time. + + + + + + Fix longstanding LISTEN/NOTIFY + race condition (Tom) + + + + In rare cases a session that had just executed a + LISTEN might not get a notification, even though + one would be expected because the concurrent transaction executing + NOTIFY was observed to commit later. + + + + A side effect of the fix is that a transaction that has executed + a not-yet-committed LISTEN command will not see any + row in pg_listener for the LISTEN, + should it choose to look; formerly it would have. This behavior + was never documented one way or the other, but it is possible that + some applications depend on the old behavior. + + + + + + Fix display of constant expressions in ORDER BY + and GROUP BY (Tom) + + + + An explictly casted constant would be shown incorrectly. This could + for example lead to corruption of a view definition during + dump and reload. + + + + + + Fix libpq to handle NOTICE messages correctly + during COPY OUT (Tom) + + + + This failure has only been observed to occur when a user-defined + datatype's output routine issues a NOTICE, but there is no + guarantee it couldn't happen due to other causes. + + + + + + + + Release 7.4.19