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

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index cd868e36d215558f5d9acd3de53b104bba5e4ece..ef0787a5a13a34223cf58af9f8deaa77e3f6058e 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -7783,7 +7783,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
        
         When set to false, which is the default, PostgreSQL
         will raise a PANIC-level error on failure to flush modified data files
-        to the filesystem.  This causes the database server to crash.
+        to the filesystem.  This causes the database server to crash.  This
+        parameter can only be set at server start.
        
        
         On some operating systems, the status of data in the kernel's page

diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index 3e68afd27502ae0706068b2a61f9931ef4d2bb6c..160011f4de39e2054d27c5d1651b17f0a4410992 100644 (file)
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -635,7 +635,9 @@
 
 #exit_on_error = off           # terminate session on any error?
 #restart_after_crash = on      # reinitialize after backend crash?
-#data_sync_retry = off         # retry or panic on failure to fsync data?
+#data_sync_retry = off         # retry or panic on failure to fsync
+                   # data?
+                   # (change requires restart)
 
 
 #------------------------------------------------------------------------------