From: Tom Lane Date: Sat, 19 Dec 2009 02:38:54 +0000 (+0000) Subject: Join in the fun of editorializing on the alpha release notes. X-Git-Tag: REL8_5_ALPHA3~11 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d2903637b897ffdba4faf79e2c95dacd5ab820ee;p=postgresql Join in the fun of editorializing on the alpha release notes. --- diff --git a/doc/src/sgml/release-8.5.sgml b/doc/src/sgml/release-8.5.sgml index 27d598f603..668c2adc2f 100644 --- a/doc/src/sgml/release-8.5.sgml +++ b/doc/src/sgml/release-8.5.sgml @@ -1,4 +1,4 @@ - + Release 8.5alpha3 @@ -55,10 +55,10 @@ Testing - The primary reason we release alphas is to get users to test new + The primary reason we release alphas is to get users to test new features as early as possible. If you are interested in helping - with organized testing, please see - the + with organized testing, please see + the testing information page. @@ -77,8 +77,8 @@ Performance and behavioral improvements in UPDATE, - DELETE, and SELECT FOR UPDATE/SHARE queries with - joins. Various corner-cases could result in duplicated output + DELETE, and SELECT FOR UPDATE/SHARE queries with joins. + Fix various corner cases that could have resulted in duplicated output rows. Set-returning functions are now prohibited in the target list of SELECT FOR UPDATE/SHARE. FOR UPDATE does not propagate into a WITH query anymore. @@ -86,7 +86,7 @@ - Fixed for SELECT FOR UPDATE/SHARE in conjuction with LIMIT. + Fix SELECT FOR UPDATE/SHARE in conjunction with LIMIT. Previously, it could return fewer rows than the limit specified. @@ -122,7 +122,7 @@ Behavioral change: formerly, agg(DISTINCT x) dropped null values of - x unconditionally. Now, it does so only if the agg transition + x unconditionally. Now, it does so only if the aggregate's transition function is strict; otherwise nulls are treated as DISTINCT normally would, i.e., you get one copy. @@ -214,12 +214,13 @@ - Allow rewriting ALTER TABLE to skip WAL logging. + Allow rewriting forms of ALTER TABLE to skip WAL + logging. - Speed up information schema privilege views. + Speed up INFORMATION_SCHEMA's privilege views. @@ -324,12 +325,6 @@ interruptions. - - - Error when a specified connection service is not found in - pg_service.conf, instead of ignoring it. - - Add YAML to list of EXPLAIN formats. @@ -474,7 +469,7 @@ Teach the regular expression functions to do case-insensitive matching and locale-dependent character classification properly when the database encoding is UTF8. This previously only worked - correct for single-byte encodings and is still broken for other + correctly for single-byte encodings. It is still broken for other multibyte encodings. @@ -583,6 +578,23 @@ + + libpq + + + + Throw error when a specified connection service name is not + found in pg_service.conf, instead of ignoring it. + + + + + Make libpq reject non-numeric and out-of-range port numbers with a + suitable error message. + + + + psql @@ -666,19 +678,31 @@ go, ie, a place where a column value or parameter would be legal, instead of the former behavior that would replace any textual match including table names and column aliases (leading to syntax errors - later on). PL/pgSQL variable names that match fully-reserved words - will now need to be quoted. On the other hand, a number of - PL/pgSQL-specific words were de-reserved. + later on). - The variable resolution behavior is by default not backward - compatible, but can be configured; see documentation. + When a name could refer either to a PL/pgSQL variable or a + table column, PL/pgSQL formerly always assumed the variable was + meant, sometimes resulting in surprising behavior. Now, PL/pgSQL + can assume the variable is meant, or assume the table column is + meant, or throw an error in ambiguous cases. For safety the default + is to throw error. To configure this see . - Error reporting is much nicer and accurate. + Error reporting is much nicer: it no longer shows edited + versions of statements that look significantly different from what + you wrote. - The argument of WHERE CURRENT OF can be a PL/pgSQL cursor variable. + Note that this change affects the set of keywords that are + reserved in PL/pgSQL (i.e., cannot be the name of a PL/pgSQL + variable). Now, all keywords shown as reserved in are reserved for PL/pgSQL purposes + as well. However, many PL/pgSQL-only keywords that were formerly + treated as reserved no longer are. As in regular SQL, you can + double-quote a variable's name if you want to use a name that + conflicts with a reserved keyword. @@ -694,9 +718,9 @@ - Python 3 support in PL/Python; behaves more or less unchanged - compared to Python 2, but the new language variant is called - plpython3u. + Add Python 3 support to PL/Python. It behaves more or less + unchanged compared to Python 2, but the new language variant is + called plpython3u. @@ -749,7 +773,7 @@ - Allow cursor commands MOVE FORWARD n, MOVE BACKWARD n, + Allow cursor commands MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE BACKWARD ALL in PL/pgSQL. @@ -780,8 +804,8 @@ Add \shell and \setshell meta commands to pgbench. - \shell command runs an external shell command. \setshell also does - the same and sets the result to a variable. + \shell runs an external shell command. \setshell + does the same and assigns the result to a variable. @@ -818,7 +842,7 @@ - Development + ecpg @@ -842,23 +866,6 @@ Make ECPG more robust against applications freeing strings. - - - Make libpq reject non-numeric and out-of-range port numbers with a - suitable error message. - - - - - Functions which conflict with C++ reserved words have been renamed, - making backend header files now safe to use with C++ libraries. - - - - - Add man pages for SPI functions. - - ECPG now includes a STRING datatype for Informix compatibility @@ -934,15 +941,21 @@ Derived files that are shipped in the distribution used to be built in the source directory even for out-of-tree - builds. They are now also built in the build tree. This + builds. They are now built in the build tree. This should be more convenient for certain developers' workflows. - - - Translations were updated. - - + + + Functions which conflict with C++ reserved words have been renamed, + making backend header files now safe to use with C++ libraries. + + + + + Add man pages for SPI functions. + + Upgrade to Autoconf 2.63 (not relevant to users of distribution