Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit1c1602b

Browse files
committed
Simplify description of --data-checksums in documentation of initdb
The documentation mentioned that data checksums cannot be changed afterinitialization, which is not true as pg_checksums can do that with its--enable option introduced in v12. This simply removes the sentencetelling so.Reported-by: Basil BourqueAuthor: Michael PaquierReviewed-by: Daniel GustafssonDiscussion:https://postgr.es/m/15909-e9d74271f1647472@postgresql.orgBackpatch-through: 12
1 parent9390747 commit1c1602b

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

‎doc/src/sgml/ref/initdb.sgml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -216,11 +216,10 @@ PostgreSQL documentation
216216
<para>
217217
Use checksums on data pages to help detect corruption by the
218218
I/O system that would otherwise be silent. Enabling checksums
219-
may incur a noticeable performance penalty. This option can only
220-
be set during initialization, and cannot be changed later. If
221-
set, checksums are calculated for all objects, in all databases. All
222-
checksum failures will be reported in the <xref
223-
linkend="pg-stat-database-view"/> view.
219+
may incur a noticeable performance penalty. If set, checksums
220+
are calculated for all objects, in all databases. All checksum
221+
failures will be reported in the
222+
<xref linkend="pg-stat-database-view"/> view.
224223
</para>
225224
</listitem>
226225
</varlistentry>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp