Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit68ab9ac

Browse files
committed
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 lessrandom ordering.
1 parent6f44fe7 commit68ab9ac

File tree

1 file changed

+113
-92
lines changed

1 file changed

+113
-92
lines changed

‎doc/src/sgml/release-10.sgml

Lines changed: 113 additions & 92 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
<formalpara>
88
<title>Release date:</title>
9-
<para>2017-??-?? (current as of 2017-09-07, commit08cb36417)</para>
9+
<para>2017-??-?? (current as of 2017-09-17, commit244b4a37e)</para>
1010
</formalpara>
1111

1212
<sect2>
@@ -157,6 +157,38 @@
157157

158158
<listitem>
159159
<!--
160+
2017-08-04 [c30f1770a] Apply ALTER ... SET NOT NULL recursively in ALTER ... AD
161+
-->
162+
<para>
163+
When <command>ALTER TABLE ... ADD PRIMARY KEY</> marks
164+
columns <literal>NOT NULL</>, that change now propagates to
165+
inheritance child tables as well (Michael Paquier)
166+
</para>
167+
</listitem>
168+
169+
<listitem>
170+
<!--
171+
2017-09-16 [54d4d0ff6] Fix SQL-spec incompatibilities in new transition table f
172+
2017-09-17 [5cc234931] Ensure that BEFORE STATEMENT triggers fire the right num
173+
-->
174+
<para>
175+
Prevent statement-level triggers from firing more than once per
176+
statement (Tom Lane)
177+
</para>
178+
179+
<para>
180+
Cases involving writable CTEs updating the same table updated by the
181+
containing statement, or by another writable CTE, fired <literal>BEFORE
182+
STATEMENT</> or <literal>AFTER STATEMENT</> triggers more than once.
183+
Also, if there were statement-level triggers on a table affected by a
184+
foreign key enforcement action (such as <literal>ON DELETE CASCADE</>),
185+
they could fire more than once per outer SQL statement. This is
186+
contrary to the SQL standard, so change it.
187+
</para>
188+
</listitem>
189+
190+
<listitem>
191+
<!--
160192
2016-12-20 [1753b1b02] Add pg_sequence system catalog
161193
2016-11-18 [67dc4ccbb] Add pg_sequences view
162194
2017-05-15 [f8dc1985f] Fix ALTER SEQUENCE locking
@@ -249,6 +281,55 @@
249281

250282
<listitem>
251283
<!--
284+
2017-03-27 [3371e4d9b] Change default of log_directory to 'log'
285+
-->
286+
<para>
287+
Change the default value of the <xref linkend="guc-log-directory">
288+
server parameter from <filename>pg_log</> to <filename>log</>
289+
(Andreas Karlsson)
290+
</para>
291+
</listitem>
292+
293+
<listitem>
294+
<!--
295+
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
296+
-->
297+
<para>
298+
Add configuration option <xref linkend="guc-ssl-dh-params-file"> to
299+
specify file name for custom OpenSSL DH parameters (Heikki Linnakangas)
300+
</para>
301+
302+
<para>
303+
This replaces the hardcoded, undocumented file
304+
name <filename>dh1024.pem</>. Note that <filename>dh1024.pem</> is
305+
no longer examined by default; you must set this option if you want
306+
to use custom DH parameters.
307+
</para>
308+
</listitem>
309+
310+
<listitem>
311+
<!--
312+
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
313+
-->
314+
<para>
315+
Increase the size of the default DH parameters used for OpenSSL
316+
ephemeral DH ciphers to 2048 bits (Heikki Linnakangas)
317+
</para>
318+
319+
<para>
320+
The size of the compiled-in DH parameters has been increased from
321+
1024 to 2048 bits, making DH key exchange more resistant to
322+
brute-force attacks. However, some old SSL implementations, notably
323+
some revisions of Java Runtime Environment version 6, will not accept
324+
DH parameters longer than 1024 bits, and hence will not be able to
325+
connect over SSL. If it's necessary to support such old clients, you
326+
can use custom 1024-bit DH parameters instead of the compiled-in
327+
defaults. See <xref linkend="guc-ssl-dh-params-file">.
328+
</para>
329+
</listitem>
330+
331+
<listitem>
332+
<!--
252333
2017-05-08 [eb61136dc] Remove support for password_encryption='off' / 'plain'.
253334
-->
254335
<para>
@@ -271,55 +352,39 @@
271352

272353
<listitem>
273354
<!--
274-
2016-10-26 [94aceed31] Support multi-dimensional arrays in PL/python.
275-
2016-10-26 [cfd9c87a5] Only treat Python Lists as array dimensions.
355+
2017-02-15 [51ee6f316] Replace min_parallel_relation_size with two new GUCs.
276356
-->
277357
<para>
278-
Allow multi-dimensional arrays to be passed into PL/Python functions,
279-
andreturned as nested Python lists (Alexey Grishchenko, Dave Cramer,
280-
Heikki Linnakangas)
358+
Add <xref linkend="guc-min-parallel-table-scan-size">
359+
and<xref linkend="guc-min-parallel-index-scan-size"> server
360+
parameters to control parallel queries (Amit Kapila, Robert Haas)
281361
</para>
282362

283363
<para>
284-
This feature requires a backwards-incompatible change to the handling
285-
of arrays of composite types in PL/Python. Previously, you could
286-
return an array of composite values by writing, e.g., <literal>[[col1,
287-
col2], [col1, col2]]</>; but now that is interpreted as a
288-
two-dimensional array. Composite types in arrays must now be written
289-
as Python tuples, not lists, to resolve the ambiguity; that is,
290-
write <literal>[(col1, col2), (col1, col2)]</> instead.
364+
These replace <varname>min_parallel_relation_size</>, which was
365+
found to be too generic.
291366
</para>
292367
</listitem>
293368

294369
<listitem>
295370
<!--
296-
2017-02-27 [817f2a586] Remove PL/Tcl's "module" facility.
371+
2017-06-20 [a69dfe5f4] Don't downcase entries within shared_preload_libraries e
297372
-->
298373
<para>
299-
Remove PL/Tcl's <quote>module</> auto-loading facility (Tom Lane)
374+
Don't downcase unquoted text
375+
within <xref linkend="guc-shared-preload-libraries"> and related
376+
server parameters (QL Zhuo)
300377
</para>
301378

302379
<para>
303-
This functionality has been replaced by new server
304-
parameters <xref linkend="guc-pltcl-start-proc">
305-
and <xref linkend="guc-pltclu-start-proc">, which are easier to use
306-
and more similar to features available in other PLs.
380+
These settings are really lists of file names, but they were
381+
previously treated as lists of SQL identifiers, which have different
382+
parsing rules.
307383
</para>
308384
</listitem>
309385

310386
<listitem>
311387
<!--
312-
2017-03-27 [3371e4d9b] Change default of log_directory to 'log'
313-
-->
314-
<para>
315-
Change the default value of the <xref linkend="guc-log-directory">
316-
server parameter from <filename>pg_log</> to <filename>log</>
317-
(Andreas Karlsson)
318-
</para>
319-
</listitem>
320-
321-
<listitem>
322-
<!--
323388
2016-12-23 [e13486eba] Remove sql_inheritance GUC.
324389
-->
325390
<para>
@@ -336,34 +401,39 @@
336401

337402
<listitem>
338403
<!--
339-
2017-02-15 [51ee6f316] Replace min_parallel_relation_size with two new GUCs.
404+
2016-10-26 [94aceed31] Support multi-dimensional arrays in PL/python.
405+
2016-10-26 [cfd9c87a5] Only treat Python Lists as array dimensions.
340406
-->
341407
<para>
342-
Add <xref linkend="guc-min-parallel-table-scan-size">
343-
and<xref linkend="guc-min-parallel-index-scan-size"> server
344-
parameters to control parallel queries (Amit Kapila, Robert Haas)
408+
Allow multi-dimensional arrays to be passed into PL/Python functions,
409+
andreturned as nested Python lists (Alexey Grishchenko, Dave Cramer,
410+
Heikki Linnakangas)
345411
</para>
346412

347413
<para>
348-
These replace <varname>min_parallel_relation_size</>, which was
349-
found to be too generic.
414+
This feature requires a backwards-incompatible change to the handling
415+
of arrays of composite types in PL/Python. Previously, you could
416+
return an array of composite values by writing, e.g., <literal>[[col1,
417+
col2], [col1, col2]]</>; but now that is interpreted as a
418+
two-dimensional array. Composite types in arrays must now be written
419+
as Python tuples, not lists, to resolve the ambiguity; that is,
420+
write <literal>[(col1, col2), (col1, col2)]</> instead.
350421
</para>
351422
</listitem>
352423

353424
<listitem>
354425
<!--
355-
2017-06-20 [a69dfe5f4] Don't downcase entries within shared_preload_libraries e
426+
2017-02-27 [817f2a586] Remove PL/Tcl's "module" facility.
356427
-->
357428
<para>
358-
Don't downcase unquoted text
359-
within <xref linkend="guc-shared-preload-libraries"> and related
360-
server parameters (QL Zhuo)
429+
Remove PL/Tcl's <quote>module</> auto-loading facility (Tom Lane)
361430
</para>
362431

363432
<para>
364-
These settings are really lists of file names, but they were
365-
previously treated as lists of SQL identifiers, which have different
366-
parsing rules.
433+
This functionality has been replaced by new server
434+
parameters <xref linkend="guc-pltcl-start-proc">
435+
and <xref linkend="guc-pltclu-start-proc">, which are easier to use
436+
and more similar to features available in other PLs.
367437
</para>
368438
</listitem>
369439

@@ -414,55 +484,6 @@
414484

415485
<listitem>
416486
<!--
417-
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
418-
-->
419-
<para>
420-
Add configuration option <xref linkend="guc-ssl-dh-params-file"> to
421-
specify file name for custom OpenSSL DH parameters (Heikki Linnakangas)
422-
</para>
423-
424-
<para>
425-
This replaces the hardcoded, undocumented file
426-
name <filename>dh1024.pem</>. Note that <filename>dh1024.pem</> is
427-
no longer examined by default; you must set this option if you want
428-
to use custom DH parameters.
429-
</para>
430-
</listitem>
431-
432-
<listitem>
433-
<!--
434-
2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
435-
-->
436-
<para>
437-
Increase the size of the default DH parameters used for OpenSSL
438-
ephemeral DH ciphers to 2048 bits (Heikki Linnakangas)
439-
</para>
440-
441-
<para>
442-
The size of the compiled-in DH parameters has been increased from
443-
1024 to 2048 bits, making DH key exchange more resistant to
444-
brute-force attacks. However, some old SSL implementations, notably
445-
some revisions of Java Runtime Environment version 6, will not accept
446-
DH parameters longer than 1024 bits, and hence will not be able to
447-
connect over SSL. If it's necessary to support such old clients, you
448-
can use custom 1024-bit DH parameters instead of the compiled-in
449-
defaults. See <xref linkend="guc-ssl-dh-params-file">.
450-
</para>
451-
</listitem>
452-
453-
<listitem>
454-
<!--
455-
2017-08-04 [c30f1770a] Apply ALTER ... SET NOT NULL recursively in ALTER ... AD
456-
-->
457-
<para>
458-
When <command>ALTER TABLE ... ADD PRIMARY KEY</> marks
459-
columns <literal>NOT NULL</>, that change now propagates to
460-
inheritance child tables as well (Michael Paquier)
461-
</para>
462-
</listitem>
463-
464-
<listitem>
465-
<!--
466487
2017-02-13 [7ada2d31f] Remove contrib/tsearch2.
467488
-->
468489
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp