Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket
Date
Msg-id CA+TgmoYoAXDtxZ7gXcV0_T1jsxVx33fdsSOSPToGX-vMZY3QTQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] possible self-deadlock window after bad ProcessStartupPacket  (Jimmy Yih <jyih@pivotal.io>)
List pgsql-hackers
Tree view 
On Thu, Feb 2, 2017 at 3:18 PM, Jimmy Yih <jyih@pivotal.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

pgsql-hackers by date:

Previous
From: Shubham Barai
Date:
Subject: Re: [HACKERS] GSoC 2017 Proposal for predicate locking in hash index
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Fast promotion not used when doing a recovery_targetPITR restore?