| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | bchen90(at)163(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16817: kill process cause postmaster hang |
| Date: | 2021-01-11 15:55:30 |
| Message-ID: | 865794.1610380530@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> 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'.
Not sure I believe this: why wouldn't the SIGKILL-after-5-seconds logic
get us out of that situation?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-01-11 19:31:48 | BUG #16818: progress reporting ALTER TABLE ADD UNIQUE |
| Previous Message | Bruce Momjian | 2021-01-11 15:21:36 | Re: pg_upgrade test for binary compatibility of core data types |