From adb1f93e73f2913bf6ff401b5c819fce85479503 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Thu, 28 Feb 2019 11:02:31 +0900 Subject: 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 --- src/backend/utils/misc/postgresql.conf.sample | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'src/backend/utils/misc/postgresql.conf.sample') 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) #------------------------------------------------------------------------------ -- cgit v1.2.3