@@ -1096,8 +1096,8 @@ Author: Thomas Munro <tmunro@postgresql.org>
10961096 </para>
10971097
10981098 <para>
1099- This only works if <literal>max_wal_senders= 0</literal>
1100- and <literal>wal_level= minimal</literal>.
1099+ This only works if <literal>max_wal_senders = 0</literal>
1100+ and <literal>wal_level = minimal</literal>.
11011101 </para>
11021102 </listitem>
11031103
@@ -1837,7 +1837,7 @@ Author: Amit Kapila <akapila@postgresql.org>
18371837 </para>
18381838
18391839 <para>
1840- In some cases a partition child table could appear more than once.
1840+ In some cases a partition could appear more than once.
18411841 </para>
18421842 </listitem>
18431843
@@ -2186,8 +2186,8 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
21862186 When applying <link
21872187 linkend="functions-datetime-zoneconvert"><literal>AT
21882188 TIME ZONE</literal></link> to a <type>time with time zone</type>
2189- value, use the transaction start time not wall clock time to
2190- determine whether DST applies (Aleksander Alekseev, Tom Lane)
2189+ value, use the transaction start time rather than wall clock time
2190+ to determine whether DST applies (Aleksander Alekseev, Tom Lane)
21912191 </para>
21922192
21932193 <para>
@@ -2480,14 +2480,15 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
24802480
24812481 <listitem>
24822482 <para>
2483- Adjust <application>psql</application> so that Readline's
2483+ Adjust <application>psql</application> so
2484+ that <application>Readline</application>'s
24842485 meta-<literal>#</literal> command will insert a double-hyphen
24852486 comment marker (Tom Lane)
24862487 </para>
24872488
24882489 <para>
2489- Previously a pound marker was inserted, but that's pretty
2490- unhelpful in SQL .
2490+ Previously a pound marker was inserted, unless the user had taken
2491+ the trouble to configure a non-default comment marker .
24912492 </para>
24922493 </listitem>
24932494
@@ -2712,7 +2713,7 @@ Author: Robert Haas <rhaas@postgresql.org>
27122713 </para>
27132714
27142715 <para>
2715- New options are <literal>server</literal> to write the
2716+ The new options are <literal>server</literal> to write the
27162717 backup locally and <literal>blackhole</literal> to discard the
27172718 backup (for testing).
27182719 </para>
@@ -2873,9 +2874,8 @@ Author: Michael Paquier <michael@paquier.xyz>
28732874
28742875 <para>
28752876 Previously such files were left in the current directory,
2876- requiring manual cleanup. It's still necessary to remove them
2877- manually afterwards, but now one can just remove that whole
2878- subdirectory.
2877+ requiring manual cleanup. Now they are automatically removed on
2878+ successful completion of <application>pg_upgrade</application>.
28792879 </para>
28802880 </listitem>
28812881
@@ -2926,7 +2926,7 @@ Author: Robert Haas <rhaas@postgresql.org>
29262926 <listitem>
29272927 <para>
29282928 Make <application>pg_upgrade</application> preserve tablespace
2929- and database OIDs, as well as table relfilenode numbers
2929+ and database OIDs, as well as relation relfilenode numbers
29302930 (Shruthi KC, Antonin Houska)
29312931 </para>
29322932 </listitem>
0 commit comments