Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Mon, 5 Feb 2001 12:36:29 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: Cygwin-Developers <cygwin-developers AT cygwin DOT com>
Cc: Yutaka tanida <yutaka AT hi-net DOT zaq DOT ne DOT jp>
Subject: Re: Cygwin CVS (or 1.1.8) fixes PostgreSQL postmaster shutdown problem
Message-ID: <20010205123629.G32580@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: Cygwin-Developers <cygwin-developers AT cygwin DOT com>,
	Yutaka tanida <yutaka AT hi-net DOT zaq DOT ne DOT jp>
References: <20010205114252 DOT H812 AT dothill DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <20010205114252.H812@dothill.com>; from Jason.Tishler@dothill.com on Mon, Feb 05, 2001 at 11:42:52AM -0500

On Mon, Feb 05, 2001 at 11:42:52AM -0500, Jason Tishler wrote:
>PostgreSQL running on 1.1.7 (and earlier) had a minor (but annoying)
>postmaster shutdown problem.  If more than one client connected
>concurrently to postmaster (i.e., the PostgreSQL backend), then
>the postmaster process would not shutdown cleanly.  By "cleanly," I
>mean that it would take a random number of "kill -s SIGTERM" attempts
>before postmaster would terminate.  Further, the greater the number of
>concurrent clients the greater the number of kills before postmaster
>would finally exit.
>
>I have been working with Yutaka tanida off and on to try to get to the
>bottom of this problem.  See attached for his latest attempt.
>
>Magically the problem seems to be solved in the latest Cygwin CVS.  Did
>someone commit a patch that would correct this problem?

It sounds like it could be some of my signal work.  I don't know for
sure.

cgf
(Mr. Cygwin Signals)