RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
Date
Msg-id EKEJJICOHDIEMGPNIFIJEELGDEAA.Inoue@tpf.co.jp
Whole thread Raw
In response to RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
Responses Re: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea
List pgsql-hackers
> -----Original Message-----
> From: Mikheev, Vadim
> 
> > I think we'd be lots better off to abandon the notion that we can exit
> > directly from the SIGTERM interrupt handler, and instead treat SIGTERM
> > the same way we treat QueryCancel: set a flag that is inspected at
> > specific places where we know we are in a good state.
> > 
> > Comments?
> 
> This will be much cleaner.
> 

Hmm, CancelQuery isn't so urgent an operation currently.
For example, VACUUM checks QueryCancel flag only
once per table.

Regards.
Hiroshi Inoue 


pgsql-hackers by date:

Previous
From: ncm@zembu.com (Nathan Myers)
Date:
Subject: Re: CRCs
Next
From: Tom Lane
Date:
Subject: Re: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad idea