{"Entry":{"collection":"guc","key":"send_abort_for_kill","name":"send_abort_for_kill","aliases":[],"metadata":{"baseline":false,"boot_human":"Not specified","boot_val":null,"category":"Developer Options","category_zh":"","changed_in":[],"changes":[{"documentation_changed":false,"fields":{},"from":"15","status":"added","to":"16"}],"content_hash":"350dcf1b7afd5e9c7f626aad4e6bd04b18567d357af303badf0d2ec6c78e5ed9","context":"","default_changed_in":[],"default_history":[{"from":"16","to":"19","value":"off"}],"editorial":{"advice":{"olap":"Long analytical runs can amplify send_abort_for_kill's debug overhead and artifacts. Prefer standard EXPLAIN and statistics first, and isolate any developer experiment from normal users.","oltp":"Do not tune production OLTP with send_abort_for_kill. Enable it only for a bounded reproduction with an owner, log/disk budget, rollback condition, and evidence-capture plan; restore the default immediately afterward.","small":"Keep send_abort_for_kill at its upstream default. A small host has less spare CPU, disk, connection, and log capacity for developer instrumentation."},"mechanism":["When a child does not exit after SIGQUIT, the postmaster normally escalates to SIGKILL after five seconds. send_abort_for_kill uses SIGABRT instead so the stuck child normally writes a core dump.","SIGABRT provides forensic state but can take time and disk space, potentially delaying crash recovery. It is not guaranteed to terminate as promptly as SIGKILL in every failure mode.","PostgreSQL does not clean generated cores. OS policy and monitoring must prevent repeated stuck processes from filling storage. Its SIGHUP context allows configuration reload without a server restart."],"pitfalls":["Leaving send_abort_for_kill enabled after the bounded diagnostic or recovery task.","Running the experiment on the only copy of production data.","Underestimating log, core-file, temporary-file, WAL, CPU, or connection-slot amplification.","Treating a server that merely starts or completes a query as proof that data and behavior are correct."],"references":[{"title":"PostgreSQL 19 Beta 4: send_abort_for_kill","url":"https://www.postgresql.org/docs/19/runtime-config-developer.html#GUC-SEND-ABORT-FOR-KILL"},{"title":"PostgreSQL 19 release notes","url":"https://www.postgresql.org/docs/19/release-19.html"}],"related":["send_abort_for_crash","remove_temp_files_after_crash","log_error_verbosity","data_directory"],"summary":"send_abort_for_kill — Send SIGABRT not SIGKILL to stuck child processes. Observed in PG16–19 Beta 4; its last measured boot default is off in PG19 Beta 4, with sighup context. This is a beta-snapshot fact and can change before PostgreSQL 19 GA."},"enumvals":[],"first_version":"16","group":"Developer Options","group_slug":"developer","imported_at":"2026-09-27T17:57:31.937233+08:00","intro_commit":{"authored_at":"2022-11-21T11:59:29-05:00","discussion":["https://postgr.es/m/2251016.1668797294@sss.pgh.pa.us"],"hash":"51b5834cd53f0bd068729043b55f7da3ca6bb15f","subject":"Provide options for postmaster to kill child processes with SIGABRT.","url":"https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=51b5834cd53f0bd068729043b55f7da3ca6bb15f"},"key":"send_abort_for_kill","last_version":"20","max_val":"","min_val":"","name":"send_abort_for_kill","position":349,"present_in":["16","17","18","19","20"],"short_desc":"By default, after attempting to stop a child process with SIGQUIT, the postmaster will wait five seconds and then send SIGKILL to force immediate termination.","short_desc_zh":"","source_rev":"english-manuals:aec71a4bc88cafaa6bd1bd3d90973486d13e9386ea493b4255ec5a9d2eb27c6c","unit":"","vartype":"bool"}},"Definition":{"Collection":"guc","Key":"send_abort_for_kill","SourceDatabase":"center","Version":"18","SourceTable":"guc","SourceKey":"send_abort_for_kill","SourceRevision":"english-manuals:aec71a4bc88cafaa6bd1bd3d90973486d13e9386ea493b4255ec5a9d2eb27c6c","Facts":{"boot_val":"off","category":"Developer Options","context":"sighup","description":"By default, after attempting to stop a child process with SIGQUIT, the postmaster will wait five seconds and then send SIGKILL to force immediate termination. When this option is set to on, SIGABRT is sent instead of SIGKILL. That normally results in production of a core dump file for each such child process. This can be handy for investigating the states of “stuck” 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 postgresql.conf file or on the server command line.","doc":{"anchor":"GUC-SEND-ABORT-FOR-KILL","file":"runtime-config-developer.html","lang":"en","sha256":"f5e7e39d176c642ac0799c87669ce2f6f60fcd97d109e290860ec74c36d7ecad","slug":"18"},"documented":true,"enumvals":null,"extra_desc":null,"lang":"en","max_val":null,"metadata_version":"18","min_val":null,"name":"send_abort_for_kill","short_desc":"Send SIGABRT not SIGKILL to stuck child processes.","source":"pg-settings-source-snapshot","unit":null,"vartype":"bool"},"ManualEvidence":{"doc":{"anchor":"GUC-SEND-ABORT-FOR-KILL","file":"runtime-config-developer.html","lang":"en","sha256":"f5e7e39d176c642ac0799c87669ce2f6f60fcd97d109e290860ec74c36d7ecad","slug":"18"}},"MeasuredEvidence":{"metadata_version":"18"}},"Text":{"Collection":"guc","Key":"send_abort_for_kill","SourceDatabase":"center","Version":"18","Locale":"en","Title":"send_abort_for_kill","Summary":"By default, after attempting to stop a child process with SIGQUIT, the postmaster will wait five seconds and then send SIGKILL to force immediate termination. When this option is set to on, SIGABRT is sent instead of SIGKILL. That normally results in production of a core dump file for each such child process. This can be handy for investigating the states of “stuck” 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 postgresql.conf file or on the server command line.","BodyHTML":"\u003cp\u003eBy default, after attempting to stop a child process with SIGQUIT, the postmaster will wait five seconds and then send SIGKILL to force immediate termination. When this option is set to on, SIGABRT is sent instead of SIGKILL. That normally results in production of a core dump file for each such child process. This can be handy for investigating the states of “stuck” 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 postgresql.conf file or on the server command line.\u003c/p\u003e","SourceRevision":"english-manuals:aec71a4bc88cafaa6bd1bd3d90973486d13e9386ea493b4255ec5a9d2eb27c6c","ContentHash":"7aa8a329f1d5305021bb9dd5d69605ec05d61db9af3ae4152dc2a4cf3768bddb","Payload":{"description":"By default, after attempting to stop a child process with SIGQUIT, the postmaster will wait five seconds and then send SIGKILL to force immediate termination. When this option is set to on, SIGABRT is sent instead of SIGKILL. That normally results in production of a core dump file for each such child process. This can be handy for investigating the states of “stuck” 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 postgresql.conf file or on the server command line."}},"RequestedLocale":"zh-Hans","Fallback":true,"Versions":["16","17","18","19","20"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}