Skip to content

Commit 00382f3

Browse files
committed
Improve documentation of data_sync_retry
Reflecting an updated parameter value requires a server restart, which was not mentioned in the documentation and in postgresql.conf.sample. Reported-by: Thomas Poty Discussion: https://postgr.es/m/15659-0cd812f13027a2d8@postgresql.org
1 parent 53c2bb7 commit 00382f3

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

doc/src/sgml/config.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6847,7 +6847,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
68476847
<para>
68486848
When set to false, which is the default, <productname>PostgreSQL</productname>
68496849
will raise a PANIC-level error on failure to flush modified data files
6850-
to the filesystem. This causes the database server to crash.
6850+
to the filesystem. This causes the database server to crash. This
6851+
parameter can only be set at server start.
68516852
</para>
68526853
<para>
68536854
On some operating systems, the status of data in the kernel's page

src/backend/utils/misc/postgresql.conf.sample

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -587,7 +587,9 @@
587587

588588
#exit_on_error = off # terminate session on any error?
589589
#restart_after_crash = on # reinitialize after backend crash?
590-
#data_sync_retry = off # retry or panic on failure to fsync data?
590+
#data_sync_retry = off # retry or panic on failure to fsync
591+
# data?
592+
# (change requires restart)
591593

592594

593595
#------------------------------------------------------------------------------

0 commit comments

Comments
 (0)