Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0bf7f56

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 d9bba27 commit 0bf7f56

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
@@ -8145,7 +8145,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
81458145
<para>
81468146
When set to false, which is the default, <productname>PostgreSQL</productname>
81478147
will raise a PANIC-level error on failure to flush modified data files
8148-
to the filesystem. This causes the database server to crash.
8148+
to the filesystem. This causes the database server to crash. This
8149+
parameter can only be set at server start.
81498150
</para>
81508151
<para>
81518152
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
@@ -665,7 +665,9 @@
665665

666666
#exit_on_error = off # terminate session on any error?
667667
#restart_after_crash = on # reinitialize after backend crash?
668-
#data_sync_retry = off # retry or panic on failure to fsync data?
668+
#data_sync_retry = off # retry or panic on failure to fsync
669+
# data?
670+
# (change requires restart)
669671

670672

671673
#------------------------------------------------------------------------------

0 commit comments

Comments
 (0)