diff options
| -rw-r--r-- | doc/src/sgml/config.sgml | 41 | ||||
| -rw-r--r-- | src/backend/utils/misc/guc.c | 5 | ||||
| -rw-r--r-- | src/backend/utils/misc/postgresql.conf.sample | 2 |
3 files changed, 22 insertions, 26 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index eeba2caa43f..f5a753e5898 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -9863,28 +9863,6 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' </listitem> </varlistentry> - <varlistentry id="guc-remove-temp-files-after-crash" xreflabel="remove_temp_files_after_crash"> - <term><varname>remove_temp_files_after_crash</varname> (<type>boolean</type>) - <indexterm> - <primary><varname>remove_temp_files_after_crash</varname> configuration parameter</primary> - </indexterm> - </term> - <listitem> - <para> - When set to <literal>on</literal>, which is the default, - <productname>PostgreSQL</productname> will automatically remove - temporary files after a backend crash. If disabled, the files will be - retained and may be used for debugging, for example. Repeated crashes - may however result in accumulation of useless files. - </para> - - <para> - This parameter can only be set in the <filename>postgresql.conf</filename> - file or on the server command line. - </para> - </listitem> - </varlistentry> - <varlistentry id="guc-data-sync-retry" xreflabel="data_sync_retry"> <term><varname>data_sync_retry</varname> (<type>boolean</type>) <indexterm> @@ -10912,6 +10890,25 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) </listitem> </varlistentry> + <varlistentry id="guc-remove-temp-files-after-crash" xreflabel="remove_temp_files_after_crash"> + <term><varname>remove_temp_files_after_crash</varname> (<type>boolean</type>) + <indexterm> + <primary><varname>remove_temp_files_after_crash</varname> configuration parameter</primary> + </indexterm> + </term> + <listitem> + <para> + When set to <literal>on</literal>, which is the default, + <productname>PostgreSQL</productname> will automatically remove + temporary files after a backend crash. If disabled, the files will be + retained and may be used for debugging, for example. Repeated crashes + may however result in accumulation of useless files. This parameter + can only be set in the <filename>postgresql.conf</filename> file or on + the server command line. + </para> + </listitem> + </varlistentry> + </variablelist> </sect1> <sect1 id="runtime-config-short"> diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c index 68b62d523dc..eaeeee58a0b 100644 --- a/src/backend/utils/misc/guc.c +++ b/src/backend/utils/misc/guc.c @@ -1404,9 +1404,10 @@ static struct config_bool ConfigureNamesBool[] = NULL, NULL, NULL }, { - {"remove_temp_files_after_crash", PGC_SIGHUP, ERROR_HANDLING_OPTIONS, + {"remove_temp_files_after_crash", PGC_SIGHUP, DEVELOPER_OPTIONS, gettext_noop("Remove temporary files after backend crash."), - NULL + NULL, + GUC_NOT_IN_SAMPLE }, &remove_temp_files_after_crash, true, diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index ddbb6dc2be2..a5a7174b0e7 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -768,8 +768,6 @@ #exit_on_error = off # terminate session on any error? #restart_after_crash = on # reinitialize after backend crash? -#remove_temp_files_after_crash = on # remove temporary files after - # backend crash? #data_sync_retry = off # retry or panic on failure to fsync # data? # (change requires restart) |