summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian2025-06-07 15:06:25 +0000
committerBruce Momjian2025-06-07 15:06:47 +0000
commit37e5f0b61fa8aad82a0b06438ed95c282ace994a (patch)
treec804086f0888ce5c1f5f3573d4c6e2de6c82f491 /doc/src
parent1a857348e47dc4f1bbf104e746abe542c99004e8 (diff)
doc PG 18 relnotes: adjust wording of initdb item 48814415d5a
And move to the top of the incompatibility list. This will impact users more than any other incompatibility item because of pg_upgrade.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/release-18.sgml39
1 files changed, 18 insertions, 21 deletions
diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml
index 19e770c65b5..268fa88cbe0 100644
--- a/doc/src/sgml/release-18.sgml
+++ b/doc/src/sgml/release-18.sgml
@@ -54,6 +54,24 @@
<itemizedlist>
<!--
+Author: Peter Eisentraut <peter@eisentraut.org>
+2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
+-->
+
+<listitem>
+<para>
+Change initdb default to enable data checksums
+<ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
+</para>
+
+<para>
+Checksums can be disabled with the new initdb option --no-data-checksums.
+pg_upgrade requires matching cluster checksum settings, so this new
+option can be useful to upgrade non-checksum old clusters.
+</para>
+</listitem>
+
+<!--
Author: Tom Lane <tgl@sss.pgh.pa.us>
2025-01-16 [d7674c9fa] Seek zone abbreviations in the IANA data before timezone
-->
@@ -194,27 +212,6 @@ These were previously zero-based.
</para>
</listitem>
-<!--
-Author: Peter Eisentraut <peter@eisentraut.org>
-2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
--->
-
-<listitem>
-<para>
-initdb defaults to enabling data checksums
-<ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
-</para>
-
-<para>
-The previous default behavior (checksums disabled) can be obtained using the
-new option --no-data-checksums. Note that pg_upgrade will reject upgrading
-between clusters with different checksum settings, so if the old cluster does
-not have checksums enabled (the previous default), then the new cluster will
-need to be initialized with --no-data-checksums in order to allow pg_upgrade
-to succeed.
-</para>
-</listitem>
-
</itemizedlist>
</sect2>