From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: bchen90@163.com
Subject: BUG #16817: kill process cause postmaster hang
Date: Mon, 11 Jan 2021 15:10:42 +0000
Message-ID: <16817-d23e3a1a027133d5@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16817
Logged by: Bo Chen
Email address: bchen90@163.com
PostgreSQL version: 11.8
Operating system: euleros v2r7 x86_64
Description:
Hi hackers
Recently we encountered a problem that after killed walwriter, we expect
the database can recover normally, but it not (the postmaster hang in the
stat of 'wait dead end',and the archiver does't exit).
After analysis this problem, we found it could be a bug for a long time.
for archiver now use 'system' to call the configed archive command. For
'system' the linux programmer's manual describe the following 'During
execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT
will be ignored'.
So, when a child chrash, we now just SIGQUIT the archiver just one time,
while the archiver just execute 'system', SIGQUIT will be ignored, then the
posmaster hang in stat of 'wait dead end'.
For this porblem, we now added a SIGUSR2 for archiver after SIGQUIT for
HandleChildCrash. If there any other solution?
regards,ChenBo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, bchen90@163.com
Subject: Re: BUG #16817: kill process cause postmaster hang
In-Reply-To: <16817-d23e3a1a027133d5@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox