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

Commitd854c7d

Browse files
committed
dummy commit
1 parentcd7569a commitd854c7d

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1696,6 +1696,15 @@ include 'filename'
16961696
turning off <varname>fsync</varname>.
16971697
</para>
16981698

1699+
<para>
1700+
For reliable recovery when changing a cluster from
1701+
<varname>fsync</varname> off to on, it is necessary to force all
1702+
modified buffers in the kernel to durable storage. This can be
1703+
done while the cluster is shutdown or while fsync is on by running
1704+
<command>initdb --sync-only</command>, running <command>sync</>,
1705+
unmounting the file system, or rebooting the server.
1706+
</para>
1707+
16991708
<para>
17001709
In many situations, turning off <xref linkend="guc-synchronous-commit">
17011710
for noncritical transactions can provide much of the potential

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp