From: Tom Lane Date: Sun, 17 Sep 2017 21:04:21 +0000 (-0400) Subject: Doc: update v10 release notes through today. X-Git-Tag: REL_11_BETA1~1575 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=68ab9acd8557a9401a115a5369a14bf0a169e8e7;p=postgresql.git Doc: update v10 release notes through today. Add item about number of times statement-level triggers will be fired. Rearrange the compatibility items into (what seems to me) a less random ordering. --- diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml index a2b1d7cd40c..2658b73ca65 100644 --- a/doc/src/sgml/release-10.sgml +++ b/doc/src/sgml/release-10.sgml @@ -6,7 +6,7 @@ Release date: - 2017-??-?? (current as of 2017-09-07, commit 08cb36417) + 2017-??-?? (current as of 2017-09-17, commit 244b4a37e) @@ -157,6 +157,38 @@ + + When ALTER TABLE ... ADD PRIMARY KEY marks + columns NOT NULL, that change now propagates to + inheritance child tables as well (Michael Paquier) + + + + + + + Prevent statement-level triggers from firing more than once per + statement (Tom Lane) + + + + Cases involving writable CTEs updating the same table updated by the + containing statement, or by another writable CTE, fired BEFORE + STATEMENT or AFTER STATEMENT triggers more than once. + Also, if there were statement-level triggers on a table affected by a + foreign key enforcement action (such as ON DELETE CASCADE), + they could fire more than once per outer SQL statement. This is + contrary to the SQL standard, so change it. + + + + + + + Change the default value of the + server parameter from pg_log to log + (Andreas Karlsson) + + + + + + + Add configuration option to + specify file name for custom OpenSSL DH parameters (Heikki Linnakangas) + + + + This replaces the hardcoded, undocumented file + name dh1024.pem. Note that dh1024.pem is + no longer examined by default; you must set this option if you want + to use custom DH parameters. + + + + + + + Increase the size of the default DH parameters used for OpenSSL + ephemeral DH ciphers to 2048 bits (Heikki Linnakangas) + + + + The size of the compiled-in DH parameters has been increased from + 1024 to 2048 bits, making DH key exchange more resistant to + brute-force attacks. However, some old SSL implementations, notably + some revisions of Java Runtime Environment version 6, will not accept + DH parameters longer than 1024 bits, and hence will not be able to + connect over SSL. If it's necessary to support such old clients, you + can use custom 1024-bit DH parameters instead of the compiled-in + defaults. See . + + + + + @@ -271,55 +352,39 @@ - Allow multi-dimensional arrays to be passed into PL/Python functions, - and returned as nested Python lists (Alexey Grishchenko, Dave Cramer, - Heikki Linnakangas) + Add + and server + parameters to control parallel queries (Amit Kapila, Robert Haas) - This feature requires a backwards-incompatible change to the handling - of arrays of composite types in PL/Python. Previously, you could - return an array of composite values by writing, e.g., [[col1, - col2], [col1, col2]]; but now that is interpreted as a - two-dimensional array. Composite types in arrays must now be written - as Python tuples, not lists, to resolve the ambiguity; that is, - write [(col1, col2), (col1, col2)] instead. + These replace min_parallel_relation_size, which was + found to be too generic. - Remove PL/Tcl's module auto-loading facility (Tom Lane) + Don't downcase unquoted text + within and related + server parameters (QL Zhuo) - This functionality has been replaced by new server - parameters - and , which are easier to use - and more similar to features available in other PLs. + These settings are really lists of file names, but they were + previously treated as lists of SQL identifiers, which have different + parsing rules. - - Change the default value of the - server parameter from pg_log to log - (Andreas Karlsson) - - - - - @@ -336,34 +401,39 @@ - Add - and server - parameters to control parallel queries (Amit Kapila, Robert Haas) + Allow multi-dimensional arrays to be passed into PL/Python functions, + and returned as nested Python lists (Alexey Grishchenko, Dave Cramer, + Heikki Linnakangas) - These replace min_parallel_relation_size, which was - found to be too generic. + This feature requires a backwards-incompatible change to the handling + of arrays of composite types in PL/Python. Previously, you could + return an array of composite values by writing, e.g., [[col1, + col2], [col1, col2]]; but now that is interpreted as a + two-dimensional array. Composite types in arrays must now be written + as Python tuples, not lists, to resolve the ambiguity; that is, + write [(col1, col2), (col1, col2)] instead. - Don't downcase unquoted text - within and related - server parameters (QL Zhuo) + Remove PL/Tcl's module auto-loading facility (Tom Lane) - These settings are really lists of file names, but they were - previously treated as lists of SQL identifiers, which have different - parsing rules. + This functionality has been replaced by new server + parameters + and , which are easier to use + and more similar to features available in other PLs. @@ -414,55 +484,6 @@ - - Add configuration option to - specify file name for custom OpenSSL DH parameters (Heikki Linnakangas) - - - - This replaces the hardcoded, undocumented file - name dh1024.pem. Note that dh1024.pem is - no longer examined by default; you must set this option if you want - to use custom DH parameters. - - - - - - - Increase the size of the default DH parameters used for OpenSSL - ephemeral DH ciphers to 2048 bits (Heikki Linnakangas) - - - - The size of the compiled-in DH parameters has been increased from - 1024 to 2048 bits, making DH key exchange more resistant to - brute-force attacks. However, some old SSL implementations, notably - some revisions of Java Runtime Environment version 6, will not accept - DH parameters longer than 1024 bits, and hence will not be able to - connect over SSL. If it's necessary to support such old clients, you - can use custom 1024-bit DH parameters instead of the compiled-in - defaults. See . - - - - - - - When ALTER TABLE ... ADD PRIMARY KEY marks - columns NOT NULL, that change now propagates to - inheritance child tables as well (Michael Paquier) - - - - -