From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Chloe Dives <Chloe(dot)Dives(at)cantabcapital(dot)com>, Chris Wilson <chris(dot)wilson(at)cantabcapital(dot)com> |
Subject: | Re: walsender bug: stuck during shutdown |
Date: | 2020-11-26 01:47:56 |
Message-ID: | f03b4b5e-5058-1cbc-f4f7-98b28fdbfa60@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020/11/26 3:45, Alvaro Herrera wrote:
> On 2020-Nov-25, Fujii Masao wrote:
>
>> But whether MyWalSnd->write is InvalidRecPtr or not, if it's behind sentPtr,
>> walsender should keep waiting for the ack to all the sent message to be
>> replied, i.e., isn't this expected behavior of normal shutdown? That is,
>> if we want to shutdown walsender even when the client side doesn't
>> reply message, immediate shutdown should be used or the client side
>> should be terminated, instead?
>
> I don't think "waiting forever" can be considered the expected behavior;
> this has caused what are nominally production outages several times
> already, since we sent a shutdown signal to the server and it never
> completed shutting down.
On the second thought, walsender doesn't wait forever unless
wal_sender_timeout is disabled, even in the case in discussion?
Or if there is the case where wal_sender_timeout doesn't work expectedly,
we might need to fix that at first.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | tsunakawa.takay@fujitsu.com | 2020-11-26 01:48:08 | RE: POC: postgres_fdw insert batching |
Previous Message | Kasahara Tatsuhito | 2020-11-26 01:41:03 | Re: autovac issue with large number of tables |