Skip to content

Commit 4881441

Browse files
committed
doc PG 18 relnotes: Add incompatibility note about checksums now default
Reviewed-by: Tomas Vondra <tomas@vondra.me> Discussion: https://www.postgresql.org/message-id/flat/CAKAnmmKwiMHik5AHmBEdf5vqzbOBbcwEPHo4-PioWeAbzwcTOQ%40mail.gmail.com
1 parent f777d77 commit 4881441

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

doc/src/sgml/release-18.sgml

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,27 @@ Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to
192192
<para>
193193
These were previously zero-based.
194194
</para>
195+
</listitem>
196+
197+
<!--
198+
Author: Peter Eisentraut <peter@eisentraut.org>
199+
2024-10-16 [04bec894a04] initdb: Change default to using data checksums.
200+
-->
201+
202+
<listitem>
203+
<para>
204+
initdb defaults to enabling data checksums
205+
<ulink url="&commit_baseurl;04bec894a04">&sect;</ulink>
206+
</para>
207+
208+
<para>
209+
The previous default behavior (checksums disabled) can be obtained using the
210+
new option --no-data-checksums. Note that pg_upgrade will reject upgrading
211+
between clusters with different checksum settings, so if the old cluster does
212+
not have checksums enabled (the previous default), then the new cluster will
213+
need to be initialized with --no-data-checksums in order to allow pg_upgrade
214+
to succeed.
215+
</para>
195216
</listitem>
196217

197218
</itemizedlist>

0 commit comments

Comments
 (0)