Re: Problem with reading startup packet after fork - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Problem with reading startup packet after fork
Date
Msg-id Pine.LNX.4.30.0106192028040.724-100000@peter.localdomain
Whole thread Raw
In response to Problem with reading startup packet after fork  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut writes:

> I think there will be a race condition around the time of a database
> shutdown.  After a new child process is created, the system may go into
> shutdown mode.  However, there is a window where the child won't know
> this, because the signal is blocked and/or not set up yet.  Note that we
> cannot check for shutdown before forking the child because we won't know
> yet whether the incoming packet is actually a connection request.  We
> wouldn't want to send back an error in response to a cancel request, for
> example.

Well, cancel that.  The child will see the shutdown because the signal is
blocked around the fork.  So unless anyone has issues with the latest
patch I posted I will check it in in slightly clean-up form.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Peter Harvey
Date:
Subject: ODBC
Next
From: Peter Eisentraut
Date:
Subject: Re: [current] readline breakage