Skip site navigation (1) Skip section navigation (2)

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

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Fred Yankowski <fred(at)ontosys(dot)com>, pgsql-cygwin(at)postgresql(dot)org
Cc: cygwin(at)cygwin(dot)com, Christopher Faylor <cgf(at)redhat(dot)com>
Subject: Re: Re: SIGTERM does not stop backend postgres processes immediately
Date: 2001-05-14 03:05:05
Message-ID: 3AFF4B61.39A0B754@tpf.co.jp (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-cygwin by date

Next:From: Henshall, Stuart - WCPDate: 2001-05-14 09:03:31
Subject: RE: C compiler cannot create executables [FROM pgsql-ports]
Previous:From: Jason TishlerDate: 2001-05-12 01:14:03
Subject: Re: Postgres server on Windows 98

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group