Re: [HACKERS] parallel.c oblivion of worker-startup failures

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(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: 2018-01-18 15:23:06
Message-ID: CA+TgmobJ2tg3bbhHoSsPZmaq9=z+2iM5y0=Jc_KiZNw8wa1OKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 21, 2017 at 9:13 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I am not against using the way specific to parallel context layer as
> described by you above. However, I was trying to see if there is
> some general purpose solution as the low-impact way is not very
> straightforward. I think you can go ahead with the way you have
> described to fix the hole I was pointing to and I can review it or I
> can also give it a try if you want to.

See attached.

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

Attachment Content-Type Size
parallel-worker-fork-failure-v2.patch application/octet-stream 7.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2018-01-18 15:54:09 Re: [HACKERS] Possible gaps/garbage in the output of XLOG reader
Previous Message Tom Lane 2018-01-18 15:19:43 Re: master make check fails on Solaris 10