2626 <itemizedlist>
2727 <listitem>
2828 <para>
29- Partitioning by a hash key
29+ Add support for partitioning by a hash key
3030 </para>
3131 </listitem>
3232 <listitem>
3333 <para>
34- Support for <literal>PRIMARY KEY</literal>, <literal>FOREIGN
34+ Add support for <literal>PRIMARY KEY</literal>, <literal>FOREIGN
3535 KEY</literal>, indexes, and triggers on partitioned tables
3636 </para>
3737 </listitem>
4444 <listitem>
4545 <para>
4646 <command>UPDATE</command> statements that change a partition key
47- column now move affected rows to the appropriate partitions
47+ column now cause affected rows to be moved to the appropriate
48+ partitions
4849 </para>
4950 </listitem>
5051 <listitem>
5152 <para>
52- Improved <command>SELECT</command> performance due to enhanced
53- partition elimination strategies during query processing
53+ Improve <command>SELECT</command> performance through enhanced
54+ partition elimination strategies during query planning and execution
5455 </para>
5556 </listitem>
5657 </itemizedlist>
116117
117118 <listitem>
118119 <para>
119- Many other useful performance improvements, including making
120- <command>ALTER TABLE ... ADD COLUMN</command> with a
121- non-null column default faster
120+ Many other useful performance improvements, including a significant
121+ speedup to <command>ALTER TABLE ... ADD COLUMN</command> with a
122+ non-null column default, as it no longer rewrites the table data
122123 </para>
123124 </listitem>
124125
187188 <application>pg_dumpall</application>'s output script will now always
188189 create databases with their original locale and encoding, and hence
189190 will fail if the locale or encoding name is unknown to the
190- destination system. Previously <command>CREATE DATABASE</command>
191+ destination system. Previously, <command>CREATE DATABASE</command>
191192 would be emitted without these specifications if the database locale
192193 and encoding matched the old cluster's defaults.
193194 </para>
307308 </para>
308309
309310 <para>
310- Previously they skipped one <emphasis>byte</emphasis> for each byte
311+ Previously, they skipped one <emphasis>byte</emphasis> for each byte
311312 of template character, resulting in strange behavior if either string
312313 contained multibyte characters.
313314 </para>
345346 <para>
346347 Per the SQL standard, relative paths start from the document node of
347348 the XML input document, not the root node as these functions
348- formerly did it .
349+ previously did.
349350 </para>
350351 </listitem>
351352
620621
621622 <para>
622623 Creation of a trigger on a partitioned table automatically creates
623- triggers on all existing partitions, and on newly-created ones .
624+ triggers on all existing and future partitions .
624625 This also allows deferred unique constraints on partitioned tables.
625626 </para>
626627 </listitem>
648649-->
649650
650651 <para>
651- Allow updated rows to automatically move to new partitions based
652- on the new row contents (Amit Khandekar)
652+ <command>UPDATE</command> statements that change a partition key
653+ column now cause affected rows to be moved to the appropriate
654+ partitions (Amit Khandekar)
653655 </para>
654656 </listitem>
655657
699701 </para>
700702
701703 <para>
702- Previously partition elimination only happened at planning
704+ Previously, partition elimination only happened at planning
703705 time, meaning many joins and prepared queries could not use
704706 partition elimination.
705707 </para>
713715-->
714716
715717 <para>
716- Allow equality joins between partitioned tables with identically
717- partitioned child tables to join the child tables directly
718- (Ashutosh Bapat)
718+ In an equality join between partitioned tables, allow matching
719+ partitions to be joined directly (Ashutosh Bapat)
719720 </para>
720721
721722 <para>
772773-->
773774
774775 <para>
775- Allow btree indexes to be built in parallel (Peter Geoghegan,
776+ Allow parallel building of a btree index (Peter Geoghegan,
776777 Rushabh Lathia, Heikki Linnakangas)
777778 </para>
778779 </listitem>
@@ -1049,7 +1050,7 @@ same commits as above
10491050 </para>
10501051
10511052 <para>
1052- Previously the most common values (<acronym>MCV</acronym>s) were
1053+ Previously, the most common values (<acronym>MCV</acronym>s) were
10531054 identified based on their frequency compared to all column
10541055 values. Now, <acronym>MCV</acronym>s are chosen based on their
10551056 frequency compared to the non-<acronym>MCV</acronym> values.
@@ -1069,7 +1070,7 @@ same commits as above
10691070 </para>
10701071
10711072 <para>
1072- Previously such cases used the same selectivity estimates
1073+ Previously, such cases used the same selectivity estimates
10731074 as <literal>></literal> and <literal><</literal>, respectively,
10741075 unless the comparison constants are <acronym>MCV</acronym>s.
10751076 This change is particularly helpful for queries
@@ -1233,7 +1234,7 @@ same commits as above
12331234 </para>
12341235
12351236 <para>
1236- Previously only non-join <command>UPDATE</command>s and
1237+ Previously, only non-join <command>UPDATE</command>s and
12371238 <command>DELETE</command>s were pushed.
12381239 </para>
12391240
@@ -1426,7 +1427,7 @@ same commits as above
14261427 <literal>pg_execute_server_program</literal>. These roles now also
14271428 control who can use server-side <command>COPY</command> and the <link
14281429 linkend="file-fdw"><filename>file_fdw</filename></link> extension.
1429- Previously only superusers could use these functions, and that
1430+ Previously, only superusers could use these functions, and that
14301431 is still the default behavior.
14311432 </para>
14321433 </listitem>
@@ -1443,7 +1444,7 @@ same commits as above
14431444 </para>
14441445
14451446 <para>
1446- Specifically, these functions were modified: <link
1447+ Specifically, these functions were modified: <link
14471448 linkend="functions-admin-genfile-table"><function>pg_ls_dir()</function></link>,
14481449 <function>pg_read_file()</function>,
14491450 <function>pg_read_binary_file()</function>,
@@ -1489,8 +1490,8 @@ same commits as above
14891490 <para>
14901491 <productname>PostgreSQL</productname> only allows superusers to
14911492 access <filename>postgres_fdw</filename> tables without
1492- passwords, e.g. via <literal>peer</literal>. Previously the
1493- session owner had to be a superuser to allow such access; now
1493+ passwords, e.g. via <literal>peer</literal>. Previously, the
1494+ session owner had to be a superuser to allow such access; now
14941495 the view owner is checked instead.
14951496 </para>
14961497 </listitem>
@@ -1594,7 +1595,7 @@ same commits as above
15941595 </para>
15951596
15961597 <para>
1597- Previously the 16MB default could only be changed at compile time.
1598+ Previously, the 16MB default could only be changed at compile time.
15981599 </para>
15991600 </listitem>
16001601
@@ -1604,13 +1605,12 @@ same commits as above
16041605-->
16051606
16061607 <para>
1607- No longer retain <acronym>WAL</acronym> that spans two checkpoints
1608+ Retain <acronym>WAL</acronym> data for only a single checkpoint
16081609 (Simon Riggs)
16091610 </para>
16101611
16111612 <para>
1612- Retention of <acronym>WAL</acronym> records is only required for one
1613- checkpoint.
1613+ Previously, <acronym>WAL</acronym> was retained for two checkpoints.
16141614 </para>
16151615 </listitem>
16161616
@@ -1685,7 +1685,7 @@ same commits as above
16851685-->
16861686
16871687 <para>
1688- Allow heap pages' checksums to be checked during streaming base
1688+ Allow checksums of heap pages to be verified during streaming base
16891689 backup (Michael Banck)
16901690 </para>
16911691 </listitem>
@@ -1965,8 +1965,8 @@ same commits as above
19651965 <para>
19661966 Allow <function>to_char()</function> and
19671967 <function>to_timestamp()</function> to specify the time zone's
1968- hours and minutes from <acronym>UTC</acronym> (Nikita Glukhov,
1969- Andrew Dunstan)
1968+ offset from <acronym>UTC</acronym> in hours and minutes
1969+ (Nikita Glukhov, Andrew Dunstan)
19701970 </para>
19711971
19721972 <para>
@@ -2094,7 +2094,7 @@ same commits as above
20942094 </para>
20952095
20962096 <para>
2097- Previously such circumstances generated errors.
2097+ Previously, such circumstances generated errors.
20982098 </para>
20992099 </listitem>
21002100
@@ -2268,7 +2268,7 @@ same commits as above
22682268 </para>
22692269
22702270 <para>
2271- Previously partition information would not be displayed for a
2271+ Previously, partition information would not be displayed for a
22722272 partitioned table if it had no partitions. Also indicate which
22732273 partitions are themselves partitioned.
22742274 </para>
@@ -2350,7 +2350,7 @@ same commits as above
23502350 </para>
23512351
23522352 <para>
2353- Previously tab completion queries could fail against older servers.
2353+ Previously, tab completion queries could fail against older servers.
23542354 </para>
23552355
23562356 </listitem>
@@ -2438,7 +2438,7 @@ same commits as above
24382438
24392439 <para>
24402440 Allow <application>pgbench</application> to do exponentiation
2441- with <function>pow()</function> and <function>power()</function>
2441+ with <function>pow()</function> and <function>power()</function>
24422442 (Raúl Marín Rodríguez)
24432443 </para>
24442444 </listitem>
@@ -2909,9 +2909,10 @@ same commits as above
29092909-->
29102910
29112911 <para>
2912- Make the computation of system column
2912+ Make the computation of
29132913 <structname>pg_class</structname>.<structfield>reltuples</structfield>
2914- more consistent (Tomas Vondra)
2914+ by <command>VACUUM</command> consistent with its computation
2915+ by <command>ANALYZE</command> (Tomas Vondra)
29152916 </para>
29162917 </listitem>
29172918
@@ -3070,7 +3071,7 @@ same commits as above
30703071 </para>
30713072
30723073 <para>
3073- Previously only superusers could call <filename>adminpack</filename>
3074+ Previously, only superusers could call <filename>adminpack</filename>
30743075 functions; now role permissions are checked.
30753076 </para>
30763077 </listitem>
0 commit comments