Re: possible self-deadlock window after bad ProcessStartupPacket

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jimmy Yih <jyih(at)pivotal(dot)io>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: possible self-deadlock window after bad ProcessStartupPacket
Date: 2017-06-22 17:33:56
Message-ID: CA+TgmoYoAXDtxZ7gXcV0_T1jsxVx33fdsSOSPToGX-vMZY3QTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 2, 2017 at 3:18 PM, Jimmy Yih <jyih(at)pivotal(dot)io> wrote:
> In that pull request, we fix the issue by checking for proc_exit_inprogress.
> Is there a reason why startup_die should not check for proc_exit_inprogress?

startup_die() is just calling proc_exit(), so it seems like it might
be better to fix it by putting the check into proc_exit itself.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-06-22 17:34:59 Re: Fast promotion not used when doing a recovery_target PITR restore?
Previous Message Shubham Barai 2017-06-22 17:32:03 Re: GSoC 2017 Proposal for predicate locking in hash index