Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit bc635dd

Browse files
tglsfdctglsfdc
committed
Doc: update v13 release notes for changes through today.
1 parent dd63a71 commit bc635dd

File tree

1 file changed

+115
-43
lines changed

1 file changed

+115
-43
lines changed

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

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

77
<formalpara>
88
<title>Release date:</title>
9-
<para>2020-XX-XX, CURRENT AS OF 2020-05-03</para>
9+
<para>2020-XX-XX, CURRENT AS OF 2020-08-09</para>
1010
</formalpara>
1111

1212
<sect2>
@@ -21,7 +21,7 @@
2121
<itemizedlist>
2222

2323
<listitem>
24-
<para></para>
24+
<para>TBD</para>
2525
</listitem>
2626

2727
</itemizedlist>
@@ -141,33 +141,18 @@ Author: Alvaro Herrera <[email protected]>
141141

142142
<listitem>
143143
<!--
144-
Author: Peter Geoghegan <[email protected]>
145-
2020-03-07 [691e8b2e1] pageinspect: Fix types used for bt_metap() columns.
146-
-->
147-
148-
<para>
149-
Fix <xref linkend="pageinspect"/>'s <function>bt_metap()</function>
150-
to return more appropriate data types that are less likely to overflow
151-
(Peter Geoghegan)
152-
</para>
153-
</listitem>
154-
155-
<listitem>
156-
<!--
157144
Author: Fujii Masao <[email protected]>
158145
2020-03-19 [1d253bae5] Rename the recovery-related wait events.
146+
Author: Tom Lane <[email protected]>
147+
2020-05-15 [36ac359d3] Rename assorted LWLock tranches.
148+
2020-05-15 [474e7da64] Change locktype "speculative token" to "spectoken".
149+
2020-05-15 [14a910109] Drop the redundant "Lock" suffix from LWLock wait event
150+
2020-05-16 [3048898e7] Mop-up for wait event naming issues.
159151
-->
160152

161153
<para>
162-
Rename some recovery-related <link linkend="wait-event-table">wait
163-
events</link> (Fujii Masao)
164-
</para>
165-
166-
<para>
167-
Rename <literal>RecoveryWalAll</literal>
168-
to <literal>RecoveryWalStream</literal>
169-
and <literal>RecoveryWalStream</literal> to
170-
<literal>RecoveryRetrieveRetryInterval</literal>.
154+
Rename various <link linkend="wait-event-table">wait
155+
events</link> to improve consistency (Fujii Masao, Tom Lane)
171156
</para>
172157
</listitem>
173158

@@ -269,6 +254,46 @@ Author: Tom Lane <[email protected]>
269254
</para>
270255
</listitem>
271256

257+
<listitem>
258+
<!--
259+
Author: Tom Lane <[email protected]>
260+
2020-06-29 [21aac2ff9] Remove support for timezone "posixrules" file.
261+
-->
262+
263+
<para>
264+
Remove support for <filename>posixrules</filename> files in the
265+
timezone database (Tom Lane)
266+
</para>
267+
268+
<para>
269+
IANA's timezone group has deprecated this feature, meaning that it
270+
will gradually disappear from systems' timezone databases over the
271+
next few years. Rather than have a behavioral change appear
272+
unexpectedly with a timezone data update, we have
273+
removed <productname>PostgreSQL</productname>'s support for this
274+
feature as of version 13. This affects only the behavior
275+
of <link linkend="datetime-posix-timezone-specs">POSIX-style time
276+
zone specifications</link> that lack an explicit daylight savings
277+
transition rule; formerly the transition rule could be determined
278+
by installing a custom <filename>posixrules</filename> file, but
279+
now it is hard-wired. The recommended fix for any affected
280+
installations is to start using a geographical time zone name.
281+
</para>
282+
</listitem>
283+
284+
<listitem>
285+
<!--
286+
Author: Peter Geoghegan <[email protected]>
287+
2020-03-07 [691e8b2e1] pageinspect: Fix types used for bt_metap() columns.
288+
-->
289+
290+
<para>
291+
Fix <xref linkend="pageinspect"/>'s <function>bt_metap()</function>
292+
to return more appropriate data types that are less likely to overflow
293+
(Peter Geoghegan)
294+
</para>
295+
</listitem>
296+
272297
</itemizedlist>
273298

274299
</sect2>
@@ -607,6 +632,8 @@ Author: Tom Lane <[email protected]>
607632
<!--
608633
Author: Tomas Vondra <[email protected]>
609634
2020-04-06 [d2d8a229b] Implement Incremental Sort
635+
Author: Peter Eisentraut <[email protected]>
636+
2020-07-05 [94e454cdd] Rename enable_incrementalsort for clarity
610637
-->
611638

612639
<para>
@@ -640,32 +667,29 @@ Author: Jeff Davis <[email protected]>
640667
2020-03-18 [1f39bce02] Disk-based Hash Aggregation.
641668
Author: Jeff Davis <[email protected]>
642669
2020-03-24 [dd8e19132] Consider disk-based hash aggregation to implement DISTIN
670+
Author: Peter Geoghegan <[email protected]>
671+
2020-07-29 [78530c8e7] Add hash_mem_multiplier GUC.
643672
-->
644673

645674
<para>
646675
Allow <link linkend="guc-enable-hashagg">hash aggregation</link>
676+
and <link linkend="queries-grouping-sets">grouping sets</link>
647677
to use disk storage for large aggregation result sets (Jeff Davis)
648678
</para>
649679

650680
<para>
651681
Previously, hash aggregation was avoided if it was expected to use
652-
more than <xref linkend="guc-work-mem"/> memory. To reduce the
653-
likelihood of using disk storage for hash aggregation and attain
654-
behavior similar to previous Postgres releases, increase <xref
655-
linkend="guc-hash-mem-multiplier"/>.
682+
more than <xref linkend="guc-work-mem"/> memory. Now, a hash
683+
aggregation plan can be chosen despite that. The hash table will
684+
be spilled to disk if it exceeds <varname>work_mem</varname> times
685+
<xref linkend="guc-hash-mem-multiplier"/>.
656686
</para>
657-
</listitem>
658-
659-
<listitem>
660-
<!--
661-
Author: Jeff Davis <[email protected]>
662-
2020-03-18 [1f39bce02] Disk-based Hash Aggregation.
663-
-->
664687

665688
<para>
666-
Allow <link linkend="queries-grouping-sets">grouping sets</link> to
667-
use hash aggregation with disk storage for large grouping set results
668-
(Jeff Davis)
689+
This behavior is normally preferable to the old behavior. But if
690+
it is inferior for a particular query, behavior similar to
691+
previous Postgres releases can be obtained by
692+
increasing <varname>hash_mem_multiplier</varname>.
669693
</para>
670694
</listitem>
671695

@@ -925,6 +949,8 @@ Author: Alvaro Herrera <[email protected]>
925949
<!--
926950
Author: Alvaro Herrera <[email protected]>
927951
2019-11-08 [71a8a4f6e] Add backtrace support for error reporting
952+
Author: Peter Eisentraut <[email protected]>
953+
2020-07-10 [8ff4d1277] Log the location field before any backtrace
928954
-->
929955

930956
<para>
@@ -1154,8 +1180,8 @@ Author: Peter Eisentraut <[email protected]>
11541180
-->
11551181

11561182
<para>
1157-
Change the default minimum <acronym>TLS</acronym> version from 1.0
1158-
to 1.2 (Peter Eisentraut)
1183+
Change the server's default minimum <acronym>TLS</acronym> version
1184+
for encrypted connections from 1.0 to 1.2 (Peter Eisentraut)
11591185
</para>
11601186

11611187
<para>
@@ -1984,7 +2010,8 @@ Author: Jeff Davis <[email protected]>
19842010
-->
19852011

19862012
<para>
1987-
Allow libpq clients to require channel binding (Jeff Davis)
2013+
Allow libpq clients to require channel binding for encrypted
2014+
connections (Jeff Davis)
19882015
</para>
19892016

19902017
<para>
@@ -2001,17 +2028,22 @@ Author: Michael Paquier <[email protected]>
20012028
2020-01-28 [ff8ca5fad] Add connection parameters to control SSL protocol min/ma
20022029
Author: Michael Paquier <[email protected]>
20032030
2020-04-30 [401aad670] Rename connection parameters to control min/max SSL prot
2031+
Author: Tom Lane <[email protected]>
2032+
2020-06-27 [16412c784] Change libpq's default ssl_min_protocol_version to TLSv1
20042033
-->
20052034

20062035
<para>
20072036
Add libpq connection parameters to control the min/max
2008-
<acronym>TLS</acronym> version (Daniel Gustafsson)
2037+
<acronym>TLS</acronym> version for encrypted connections
2038+
(Daniel Gustafsson)
20092039
</para>
20102040

20112041
<para>
20122042
The settings are <xref
20132043
linkend="libpq-connect-ssl-min-protocol-version"/> and <xref
20142044
linkend="libpq-connect-ssl-max-protocol-version"/>.
2045+
By default, the minimum <acronym>TLS</acronym> version is 1.2
2046+
(this represents a behavioral change from previous releases).
20152047
</para>
20162048
</listitem>
20172049

@@ -2022,7 +2054,7 @@ Author: Fujii Masao <[email protected]>
20222054
-->
20232055

20242056
<para>
2025-
Tighten line length and comment detection in <link
2057+
Tighten libpq's overlength-line handling and comment detection for <link
20262058
linkend="libpq-pgpass">.pgpass</link> files (Fujii Masao)
20272059
</para>
20282060
</listitem>
@@ -2056,6 +2088,26 @@ Author: Andrew Dunstan <[email protected]>
20562088
</para>
20572089
</listitem>
20582090

2091+
<listitem>
2092+
<!--
2093+
Author: Tom Lane <[email protected]>
2094+
2020-08-03 [44cd434ec] Fix behavior of ecpg's "EXEC SQL elif name".
2095+
-->
2096+
2097+
<para>
2098+
Fix <application>ecpg</application>'s <literal>EXEC SQL
2099+
elif</literal> directive to work correctly (Tom Lane)
2100+
</para>
2101+
2102+
<para>
2103+
Previously it behaved the same as <literal>endif</literal> followed
2104+
by <literal>ifdef</literal>, so that a successful previous branch
2105+
of the same <literal>if</literal> construct did not prevent
2106+
expansion of the <literal>elif</literal> branch or following
2107+
branches.
2108+
</para>
2109+
</listitem>
2110+
20592111
</itemizedlist>
20602112

20612113
</sect3>
@@ -2798,6 +2850,25 @@ Author: Michael Paquier <[email protected]>
27982850
</para>
27992851
</listitem>
28002852

2853+
<listitem>
2854+
<!--
2855+
Author: Tom Lane <[email protected]>
2856+
2020-07-24 [92fe6895d] Fix assorted bugs by changing TS_execute's callback API
2857+
2020-07-24 [70eca6a9a] Replace TS_execute's TS_EXEC_CALC_NOT flag with TS_EXEC_
2858+
-->
2859+
2860+
<para>
2861+
Change the API for <function>TS_execute()</function> (Tom Lane,
2862+
Pavel Borisov)
2863+
</para>
2864+
2865+
<para>
2866+
<function>TS_execute</function> callbacks must now provide ternary
2867+
(yes/no/maybe) logic. Calculating NOT queries accurately is now
2868+
the default.
2869+
</para>
2870+
</listitem>
2871+
28012872
</itemizedlist>
28022873

28032874
</sect3>
@@ -2915,6 +2986,7 @@ Author: Andrew Gierth <[email protected]>
29152986
<!--
29162987
Author: Fujii Masao <[email protected]>
29172988
2020-04-02 [17e032822] Allow pg_stat_statements to track planning statistics.
2989+
2020-07-03 [8d459762b] Change default of pg_stat_statements.track_planning to o
29182990
-->
29192991

29202992
<para>

0 commit comments

Comments
 (0)