diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 56 | ||||
| -rw-r--r-- | doc/src/sgml/ref/postgres-ref.sgml | 29 |
2 files changed, 59 insertions, 26 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index bd50ea8e480..24b1624bad1 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -11500,6 +11500,62 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) </listitem> </varlistentry> + <varlistentry id="guc-send-abort-for-crash" xreflabel="send_abort_for_crash"> + <term><varname>send_abort_for_crash</varname> (<type>boolean</type>) + <indexterm> + <primary><varname>send_abort_for_crash</varname> configuration parameter</primary> + </indexterm> + </term> + <listitem> + <para> + By default, after a backend crash the postmaster will stop remaining + child processes by sending them <systemitem>SIGQUIT</systemitem> + signals, which permits them to exit more-or-less gracefully. When + this option is set to <literal>on</literal>, + <systemitem>SIGABRT</systemitem> is sent instead. That normally + results in production of a core dump file for each such child + process. + This can be handy for investigating the states of other processes + after a crash. It can also consume lots of disk space in the event + of repeated crashes, so do not enable this on systems you are not + monitoring carefully. + Beware that no support exists for cleaning up the core file(s) + automatically. + 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-send-abort-for-kill" xreflabel="send_abort_for_kill"> + <term><varname>send_abort_for_kill</varname> (<type>boolean</type>) + <indexterm> + <primary><varname>send_abort_for_kill</varname> configuration parameter</primary> + </indexterm> + </term> + <listitem> + <para> + By default, after attempting to stop a child process with + <systemitem>SIGQUIT</systemitem>, the postmaster will wait five + seconds and then send <systemitem>SIGKILL</systemitem> to force + immediate termination. When this option is set + to <literal>on</literal>, <systemitem>SIGABRT</systemitem> is sent + instead of <systemitem>SIGKILL</systemitem>. That normally results + in production of a core dump file for each such child process. + This can be handy for investigating the states + of <quote>stuck</quote> child processes. It can also consume lots + of disk space in the event of repeated crashes, so do not enable + this on systems you are not monitoring carefully. + Beware that no support exists for cleaning up the core file(s) + automatically. + 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/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 55a3f6c69d1..b13a16a117f 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -410,24 +410,6 @@ PostgreSQL documentation </varlistentry> <varlistentry> - <term><option>-n</option></term> - <listitem> - <para> - This option is for debugging problems that cause a server - process to die abnormally. The ordinary strategy in this - situation is to notify all other server processes that they - must terminate and then reinitialize the shared memory and - semaphores. This is because an errant server process could - have corrupted some shared state before terminating. This - option specifies that <command>postgres</command> will - not reinitialize shared data structures. A knowledgeable - system programmer can then use a debugger to examine shared - memory and semaphore state. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>-O</option></term> <listitem> <para> @@ -466,14 +448,9 @@ PostgreSQL documentation This option is for debugging problems that cause a server process to die abnormally. The ordinary strategy in this situation is to notify all other server processes that they - must terminate and then reinitialize the shared memory and - semaphores. This is because an errant server process could - have corrupted some shared state before terminating. This - option specifies that <command>postgres</command> will - stop all other server processes by sending the signal - <literal>SIGSTOP</literal>, but will not cause them to - terminate. This permits system programmers to collect core - dumps from all server processes by hand. + must terminate, by sending them <systemitem>SIGQUIT</systemitem> + signals. With this option, <systemitem>SIGABRT</systemitem> + will be sent instead, resulting in production of core dump files. </para> </listitem> </varlistentry> |