Re: Re: SIGTERM does not stop backend postgres processes immediately - Mailing list pgsql-cygwin

From Hiroshi Inoue
Subject Re: Re: SIGTERM does not stop backend postgres processes immediately
Date
Msg-id 3AFF4B61.39A0B754@tpf.co.jp
Whole thread Raw
In response to Re: SIGTERM does not stop backend postgres processes immediately  (Fred Yankowski <fred@ontosys.com>)
List pgsql-cygwin
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

pgsql-cygwin by date:

Previous
From: Jason Tishler
Date:
Subject: Re: Postgres server on Windows 98
Next
From: "Henshall, Stuart - WCP"
Date:
Subject: RE: C compiler cannot create executables [FROM pgsql-ports]