From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] parallel.c oblivion of worker-startup failures |
Date: | 2017-12-12 03:41:25 |
Message-ID: | CAA4eK1+y2asrJRS3XG2Pwwy8_Ypcv=arrL33_8U0Bj9hY9Hpeg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 12, 2017 at 9:00 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Mon, Dec 11, 2017 at 11:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Sun, Dec 10, 2017 at 11:07 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>>> Okay, see the attached and let me know if that suffices the need?
>>
>> + * Check for unexpected worker death. This will ensure that if
>> + * the postmaster failed to start the worker, then we don't wait
>> + * for it indefinitely. For workers that are known to be
>> + * launched, we can rely on their error queue being freed once
>> + * they exit.
>>
>> Hmm. Is this really true? What if the worker starts up but then
>> crashes before attaching to the error queue?
>>
>
> If the worker errored out before attaching to the error queue, then we
> can't rely on error queue being freed. However, in that case, the
> worker status will be BGWH_STOPPED. I have adjusted the comment
> accordingly.
>
In particular, if the worker crashed (say somebody forcefully killed
the worker), then I think it will lead to a restart of the server. So
not sure, adding anything about that in the comment will make much
sense.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-12-12 03:57:41 | Using ProcSignal to get memory context stats from a running backend |
Previous Message | Masahiko Sawada | 2017-12-12 03:41:01 | Re: BUG #14941: Vacuum crashes |