Re: Immediate shutdown and system(3) - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Immediate shutdown and system(3)
Date
Msg-id 49AB91F0.2010304@enterprisedb.com
Whole thread Raw
In response to Re: Immediate shutdown and system(3)  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Immediate shutdown and system(3)  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Re: Immediate shutdown and system(3)  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Fujii Masao wrote:
> On Fri, Feb 27, 2009 at 6:52 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> wrote:
>> I'm leaning towards option 3, but I wonder if anyone sees a better solution.
> 
> 4. Use the shared memory to tell the startup process about the shutdown state.
> When a shutdown signal arrives, postmaster sets the corresponding shutdown
> state to the shared memory before signaling to the child processes. The startup
> process check the shutdown state whenever executing system(), and determine
> how to exit according to that state. This solution doesn't change any existing
> behavior of pg_standby. What is your opinion?

That would only solve the problem for pg_standby. Other programs you 
might use as a restore_command or archive_command like "cp" or "rsync" 
would still core dump on the SIGQUIT.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: WIP: named and mixed notation support
Next
From: Peter Eisentraut
Date:
Subject: Re: xpath processing brain dead