Prev: [HACKERS] How to know killed by pg_terminate_backend
Next: [HACKERS] recovery getting interrupted is not so unusual as it used to be
From: Robert Haas on 12 May 2010 20:48
On Wed, May 12, 2010 at 3:55 PM, Robert Haas <robertmhaas(a)gmail.com> wrote:
> I am wondering if we are not correctly handling the case where we get
> a shutdown request while we are still in the PM_STARTUP state.  It
> looks like we might go ahead and switch to PM_RECOVERY and then
> PM_RECOVERY_CONSISTENT without noticing the shutdown.  There is some
> logic to handle the shutdown when the startup process exits, but if
> the startup process never exits it looks like we might get stuck.

I can reproduce the behavior Stefan is seeing consistently using the
attached patch.

W1: postgres -D ~/pgslave
W2: pg_ctl -D ~/pgslave stop

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
 | 
Pages: 1
Prev: [HACKERS] How to know killed by pg_terminate_backend
Next: [HACKERS] recovery getting interrupted is not so unusual as it used to be