send_abort_for_kill

doc html

<p>
        By default, after attempting to stop a child process with
        <span class="systemitem">SIGQUIT</span>, the postmaster will wait five
        seconds and then send <span class="systemitem">SIGKILL</span> to force
        immediate termination.  When this option is set
        to <code class="literal">on</code>, <span class="systemitem">SIGABRT</span> is sent
        instead of <span class="systemitem">SIGKILL</span>.  That normally results
        in production of a core dump file for each such child process.
        This can be handy for investigating the states
        of <span class="quote">“<span class="quote">stuck</span>”</span> 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 <code class="filename">postgresql.conf</code> file or on the server
        command line.
       </p>

documentation revision

{"inputs":[{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"a3f6a107ed6ba4edaf6df03e52f4a469bd09350d545e4ff419e62844025ec1cf","version":"18.7"},{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"e7e22aa5738a1d376b84af1adca796c5e14746266733f925eb50c3ef86a50655","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}