Skip to content

P
Postgres FD Implementation
Commit 68ab9acd authored by Tom Lane's avatar Tom Lane
Browse files
Options

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.
parent 6f44fe7f
Show whitespace changes
Inline Side-by-side
Showing with 113 additions and 92 deletions
doc/src/sgml/release-10.sgml
View file @ 68ab9acd
......@@ -6,7 +6,7 @@
<formalpara>
<title>Release date:</title>
<para>2017-??-?? (current as of 2017-09-07, commit 08cb36417)</para>
<para>2017-??-?? (current as of 2017-09-17, commit 244b4a37e)</para>
</formalpara>
<sect2>
......@@ -157,6 +157,38 @@
<listitem>
<!--
2017-08-04 [c30f1770a] Apply ALTER ... SET NOT NULL recursively in ALTER ... AD
-->
<para>
When <command>ALTER TABLE ... ADD PRIMARY KEY</> marks
columns <literal>NOT NULL</>, that change now propagates to
inheritance child tables as well (Michael Paquier)
</para>
</listitem>
<listitem>
<!--
2017-09-16 [54d4d0ff6] Fix SQL-spec incompatibilities in new transition table f
2017-09-17 [5cc234931] Ensure that BEFORE STATEMENT triggers fire the right num
-->
<para>
Prevent statement-level triggers from firing more than once per
statement (Tom Lane)
</para>
<para>
Cases involving writable CTEs updating the same table updated by the
containing statement, or by another writable CTE, fired <literal>BEFORE
STATEMENT</> or <literal>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 <literal>ON DELETE CASCADE</>),
they could fire more than once per outer SQL statement. This is
contrary to the SQL standard, so change it.
</para>
</listitem>
<listitem>
<!--
2016-12-20 [1753b1b02] Add pg_sequence system catalog
2016-11-18 [67dc4ccbb] Add pg_sequences view
2017-05-15 [f8dc1985f] Fix ALTER SEQUENCE locking
......@@ -249,88 +281,72 @@
<listitem>
<!--
2017-05-08 [eb61136dc] Remove support for password_encryption='off' / 'plain'.
2017-03-27 [3371e4d9b] Change default of log_directory to 'log'
-->
<para>
Remove the ability to store unencrypted passwords on the server
(Heikki Linnakangas)
</para>
<para>
The <xref linkend="guc-password-encryption"> server parameter
no longer supports <literal>off</> or <literal>plain</>.
The <literal>UNENCRYPTED</> option is no longer supported in
<command>CREATE/ALTER USER ... PASSSWORD</>. Similarly, the
<option>--unencrypted</> option has been removed
from <application>createuser</>. Unencrypted passwords migrated from
older versions will be stored encrypted in this release. The default
setting for <varname>password_encryption</> is still
<literal>md5</>.
Change the default value of the <xref linkend="guc-log-directory">
server parameter from <filename>pg_log</> to <filename>log</>
(Andreas Karlsson)
</para>
</listitem>
<listitem>
<!--
2016-10-26 [94aceed31] Support multi-dimensional arrays in PL/python.
2016-10-26 [cfd9c87a5] Only treat Python Lists as array dimensions.
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
-->
<para>
Allow multi-dimensional arrays to be passed into PL/Python functions,
and returned as nested Python lists (Alexey Grishchenko, Dave Cramer,
Heikki Linnakangas)
Add configuration option <xref linkend="guc-ssl-dh-params-file"> to
specify file name for custom OpenSSL DH parameters (Heikki Linnakangas)
</para>
<para>
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., <literal>[[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 <literal>[(col1, col2), (col1, col2)]</> instead.
This replaces the hardcoded, undocumented file
name <filename>dh1024.pem</>. Note that <filename>dh1024.pem</> is
no longer examined by default; you must set this option if you want
to use custom DH parameters.
</para>
</listitem>
<listitem>
<!--
2017-02-27 [817f2a586] Remove PL/Tcl's "module" facility.
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
-->
<para>
Remove PL/Tcl's <quote>module</> auto-loading facility (Tom Lane)
</para>
<para>
This functionality has been replaced by new server
parameters <xref linkend="guc-pltcl-start-proc">
and <xref linkend="guc-pltclu-start-proc">, which are easier to use
and more similar to features available in other PLs.
Increase the size of the default DH parameters used for OpenSSL
ephemeral DH ciphers to 2048 bits (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<!--
2017-03-27 [3371e4d9b] Change default of log_directory to 'log'
-->
<para>
Change the default value of the <xref linkend="guc-log-directory">
server parameter from <filename>pg_log</> to <filename>log</>
(Andreas Karlsson)
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 <xref linkend="guc-ssl-dh-params-file">.
</para>
</listitem>
<listitem>
<!--
2016-12-23 [e13486eba] Remove sql_inheritance GUC.
2017-05-08 [eb61136dc] Remove support for password_encryption='off' / 'plain'.
-->
<para>
Remove <varname>sql_inheritance</> server parameter (Robert Haas)
Remove the ability to store unencrypted passwords on the server
(Heikki Linnakangas)
</para>
<para>
Changing this setting from the default value caused queries referencing
parent tables to not include child tables. The <acronym>SQL</>
standard requires them to be included, however, and this has been the
default since <productname>PostgreSQL</> 7.1.
The <xref linkend="guc-password-encryption"> server parameter
no longer supports <literal>off</> or <literal>plain</>.
The <literal>UNENCRYPTED</> option is no longer supported in
<command>CREATE/ALTER USER ... PASSSWORD</>. Similarly, the
<option>--unencrypted</> option has been removed
from <application>createuser</>. Unencrypted passwords migrated from
older versions will be stored encrypted in this release. The default
setting for <varname>password_encryption</> is still
<literal>md5</>.
</para>
</listitem>
......@@ -369,95 +385,100 @@
<listitem>
<!--
2016-10-12 [64f3524e2] Remove pg_dump/pg_dumpall support for dumping from pre-8
2016-12-23 [e13486eba] Remove sql_inheritance GUC.
-->
<para>
Remove <application>pg_dump</>/<application>pg_dumpall</> support
for dumping from pre-8.0 servers (Tom Lane)
Remove <varname>sql_inheritance</> server parameter (Robert Haas)
</para>
<para>
Users needing to dump from pre-8.0 servers will need to use dump
programs from <productname>PostgreSQL</> 9.6 or earlier. The
resulting output should still load successfully into newer servers.
Changing this setting from the default value caused queries referencing
parent tables to not include child tables. The <acronym>SQL</>
standard requires them to be included, however, and this has been the
default since <productname>PostgreSQL</> 7.1.
</para>
</listitem>
<listitem>
<!--
2017-02-23 [b6aa17e0a] De-support floating-point timestamps.
2016-10-26 [94aceed31] Support multi-dimensional arrays in PL/python.
2016-10-26 [cfd9c87a5] Only treat Python Lists as array dimensions.
-->
<para>
Remove support for floating-point timestamps and intervals (Tom Lane)
Allow multi-dimensional arrays to be passed into PL/Python functions,
and returned as nested Python lists (Alexey Grishchenko, Dave Cramer,
Heikki Linnakangas)
</para>
<para>
This removes configure's <option>--disable-integer-datetimes</>
option. Floating-point timestamps have few advantages and have not
been the default since <productname>PostgreSQL</> 8.3.
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., <literal>[[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 <literal>[(col1, col2), (col1, col2)]</> instead.
</para>
</listitem>
<listitem>
<!--
2016-10-11 [2f1eaf87e] Drop server support for FE/BE protocol version 1.0.
2017-02-27 [817f2a586] Remove PL/Tcl's "module" facility.
-->
<para>
Remove server support for client/server protocol version 1.0 (Tom Lane)
Remove PL/Tcl's <quote>module</> auto-loading facility (Tom Lane)
</para>
<para>
This protocol hasn't had client support
since <productname>PostgreSQL</> 6.3.
This functionality has been replaced by new server
parameters <xref linkend="guc-pltcl-start-proc">
and <xref linkend="guc-pltclu-start-proc">, which are easier to use
and more similar to features available in other PLs.
</para>
</listitem>
<listitem>
<!--
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
2016-10-12 [64f3524e2] Remove pg_dump/pg_dumpall support for dumping from pre-8
-->
<para>
Add configuration option <xref linkend="guc-ssl-dh-params-file"> to
specify file name for custom OpenSSL DH parameters (Heikki Linnakangas)
Remove <application>pg_dump</>/<application>pg_dumpall</> support
for dumping from pre-8.0 servers (Tom Lane)
</para>
<para>
This replaces the hardcoded, undocumented file
name <filename>dh1024.pem</>. Note that <filename>dh1024.pem</> is
no longer examined by default; you must set this option if you want
to use custom DH parameters.
Users needing to dump from pre-8.0 servers will need to use dump
programs from <productname>PostgreSQL</> 9.6 or earlier. The
resulting output should still load successfully into newer servers.
</para>
</listitem>
<listitem>
<!--
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
2017-02-23 [b6aa17e0a] De-support floating-point timestamps.
-->
<para>
Increase the size of the default DH parameters used for OpenSSL
ephemeral DH ciphers to 2048 bits (Heikki Linnakangas)
Remove support for floating-point timestamps and intervals (Tom Lane)
</para>
<para>
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 <xref linkend="guc-ssl-dh-params-file">.
This removes configure's <option>--disable-integer-datetimes</>
option. Floating-point timestamps have few advantages and have not
been the default since <productname>PostgreSQL</> 8.3.
</para>
</listitem>
<listitem>
<!--
2017-08-04 [c30f1770a] Apply ALTER ... SET NOT NULL recursively in ALTER ... AD
2016-10-11 [2f1eaf87e] Drop server support for FE/BE protocol version 1.0.
-->
<para>
When <command>ALTER TABLE ... ADD PRIMARY KEY</> marks
columns <literal>NOT NULL</>, that change now propagates to
inheritance child tables as well (Michael Paquier)
Remove server support for client/server protocol version 1.0 (Tom Lane)
</para>
<para>
This protocol hasn't had client support
since <productname>PostgreSQL</> 6.3.
</para>
</listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment