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

From Peter Eisentraut
Subject Problem with reading startup packet after fork
Date
Msg-id Pine.LNX.4.30.0106181846490.898-100000@peter.localdomain
Whole thread Raw
Responses Re: Problem with reading startup packet after fork  (Peter Eisentraut <peter_e@gmx.net>)
Re: Problem with reading startup packet after fork  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.

Any ideas?

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



pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: [BUGS] Update is not atomic
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Re: Re: REPLACE INTO table a la mySQL