Postgres Pro
Downloads
Home   >   mailing lists

Re: "wal receiver" process hang in syslog() while exiting afterreceiving SIGTERM while the postgres has been promoted. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: "wal receiver" process hang in syslog() while exiting afterreceiving SIGTERM while the postgres has been promoted.
Date
Msg-id CA+TgmoaWDfGs=iWePrfxa5HWwW7ZX7MadAsn8i4Dcxoa5-vNVw@mail.gmail.com
Whole thread Raw
In response to "wal receiver" process hang in syslog() while exiting after receivingSIGTERM while the postgres has been promoted.  ("Chen, Yan-Jack (NSB - CN/Hangzhou)" <yan-jack.chen@nokia-sbell.com>)
Responses RE: "wal receiver" process hang in syslog() while exiting afterreceiving SIGTERM while the postgres has been promoted.
List pgsql-hackers
Tree view 
On Thu, Jun 21, 2018 at 1:11 AM, Chen, Yan-Jack (NSB - CN/Hangzhou)
<yan-jack.chen@nokia-sbell.com> wrote:
> Hi Hackers,
>   We encounter one problem happened while we try to promote standby
> postgres(version 9.6.9) server to active. From the trace(we triggered the
> process abort). We can see the process was hang in syslog() while handling
> SIGTERM. According to below article. Looks it is risky to write syslog in
> signal handling. Any idea to avoid it?

Huh.  I thought that Andres had removed all of this kind of stuff back
in 6753333f55e1d9bcb9da4323556b456583624a07,
4f85fde8eb860f263384fffdca660e16e77c7f76, and
387da18874afa17156ee3af63766f17efb53c4b9, and related commits, but
rereading the commit message I see that it wasn't that ambitious.
Probably a similar approach would make sense here, though.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Fix some error handling for read() and errno
Next
From: Andrew Dunstan
Date:
Subject: Re: Fast default stuff versus pg_upgrade