Wiki / 配置参数

By default, after a backend crash the postmaster will stop remaining child processes by sending them SIGQUIT signals, which permits them to exit more-or-less gracefully. When this option is set to on, SIGABRT 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 postgresql.conf file or on the server command line.

英文手册覆盖始于 PostgreSQL 7.4. 来源历史与运行验证各自保留独立版本边界。

此版本暂无所选语言的定义，以下显示原始英文内容。

boot val

off

category

Developer Options

context

sighup

documented

true

enumvals

未知

extra desc

未知

lang

en

max val

未知

metadata version

18

min val

未知

name

send_abort_for_crash

short desc

Send SIGABRT not SIGQUIT to child processes after backend crash.

source

pg-settings-source-snapshot

unit

未知

vartype

bool