summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier2019-02-28 02:02:31 +0000
committerMichael Paquier2019-02-28 02:02:31 +0000
commitadb1f93e73f2913bf6ff401b5c819fce85479503 (patch)
tree3b9fb50c2b2c0b16bff65e240619db843d1f08e2
parent904fce2a7695521d2cf25a3a08676f3c96d4096c (diff)
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
-rw-r--r--doc/src/sgml/config.sgml3
-rw-r--r--src/backend/utils/misc/postgresql.conf.sample4
2 files changed, 5 insertions, 2 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index f59428f6f2c..c485f4635db 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -7530,7 +7530,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
<para>
When set to false, which is the default, <productname>PostgreSQL</productname>
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.
</para>
<para>
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 756dfb396a7..b8d7d857108 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -620,7 +620,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)
#------------------------------------------------------------------------------