[CYGWIN] Re: SIGTERM does not stop backend postgres processes immediately

Hiroshi Inoue Inoue@tpf.co.jp
Sun May 13 20:04:00 GMT 2001


Christopher Faylor wrote:
> 
> On Wed, May 09, 2001 at 02:26:29PM -0400, Jason Tishler wrote:
> >> I know from inserting printfs into the backend code that the SIGTERM
> >> signal handler function is not being called right after the stop
> >> request.  Rather, it is called only after the backend gets some data
> >> over its input socket connection, from that "\d" in did in pg_ctl in
> >> this case.  It seems that the recv() call deep in the backend code
> >> does not get interrupted by the SIGTERM.
> >

How about inserting a select() call before the recv() ?
Cygwin's select() is interruptible AFAIK.

regards,
Hiroshi Inoue

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


More information about the Cygwin mailing list