pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: bchen90@163.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16817: kill process cause postmaster hang
Date: Mon, 11 Jan 2021 10:55:30 -0500
Message-ID: <865794.1610380530@sss.pgh.pa.us> (raw)
In-Reply-To: <16817-d23e3a1a027133d5@postgresql.org>
References: <16817-d23e3a1a027133d5@postgresql.org>

PG Bug reporting form <noreply@postgresql.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





view thread (5+ messages)  latest in thread

Message-ID: <865794.1610380530@sss.pgh.pa.us>
Permalink:  ../865794.1610380530@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/865794.1610380530@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, bchen90@163.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16817: kill process cause postmaster hang
  In-Reply-To: <865794.1610380530@sss.pgh.pa.us>

* 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