Re: Re: SIGTERM does not stop backend postgres processes immediately

Hiroshi,

On Tue, May 15, 2001 at 10:30:39AM +0900, Hiroshi Inoue wrote:
> Hiroshi Inoue wrote:
> > 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.
>
> I see the following reply from Chris in cygwin's archive(I'm not
> the member).
>
>   That would be the "workaround" that I kept mentioning previously.
>   It relies on polling and that is a something I'd rather avoid, if
>   possible.
>
> My proposal is to pgsql-cygwin not to cygwin from the first.
> The following is an example.
>
> Comments ?
>
> [patch snipped]

Your patch is no longer needed since Cygwin's recv in now interruptible.
See the following for details:

    http://cygwin.com/ml/cygwin/2001-05/msg00752.html
    http://cygwin.com/ml/cygwin/2001-05/msg00774.html

Although, I do appreciate your efforts trying to come up with a
workaround.

Thanks,
Jason

--
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp.               Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com