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

(Cygwin) postmaster shutdown problem

From: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
To: pgsql-ports(at)postgresql(dot)org
Subject: (Cygwin) postmaster shutdown problem
Date: 2001-01-05 19:13:11
Message-ID: 20010105141310.A444@dothill.com (view raw or flat)
Thread:
Lists: pgsql-ports
I am observing the following postmaster shutdown problem with 7.0.3 and
the 12/29/2000 snapshot on Cygwin 1.1.7:

    After postmaster has been driven by multiple simultaneous (JDBC)
    connections, postmaster usually requires to receive more the one
    SIGTERM signal before it will perform a Smart Shutdown.

When I run the 7.0.3 postmaster with the "-d 1" option, I get the
following pruned and annotated (indicated by the ### prefix) output for
two simultaneous connections:

    ...
    ### last JDBC connection is dropped by client
    pq_recvbuf: recv() failed: Connection reset by peer
    proc_exit(0)
    shmem_exit(0)
    exit(0)
    /usr/local/pgsql/bin/postmaster: reaping dead processes...
    /usr/local/pgsql/bin/postmaster: CleanupProc: pid 461 exited with status 0
    /usr/local/pgsql/bin/postmaster: CleanupProc: pid 406 exited with status 0
    /usr/local/pgsql/bin/postmaster: CleanupProc: pid 358 exited with status 0
    /usr/local/pgsql/bin/postmaster: reaping dead processes...
    ### first SIGTERM signal received
    /usr/local/pgsql/bin/postmaster: reaping dead processes...
    /usr/local/pgsql/bin/postmaster: reaping dead processes...
    ### second SIGTERM signal received
    pmdie 15
    Smart Shutdown request at Fri Jan  5 13:47:13 2001
    ...

The above output seems to indicate that reaper() is firing instead of
pmdie() when the first SIGTERM is signal received.  Hmm...

If postmaster is driven by only one connection, then it always shutdowns
on the first SIGTERM signal.  If postmaster is driven by more than two
connections, then it can require three or more SIGTERM signals.

I have *not* been able to reproduce this problem with 7.0.3 on Red Hat
6.2 Linux.

Is this a known problem?  Has anyone else observed this problem on a
platform other than Cygwin?  This information would be helpful before I
start trudging through the Cygwin DLL...

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(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

Responses

pgsql-ports by date

Next:From: Yutaka tanidaDate: 2001-01-06 11:58:48
Subject: Re: (Cygwin) postmaster shutdown problem
Previous:From: David TrustyDate: 2001-01-05 01:22:22
Subject: Porting problem (and fix) for Solaris 8 intel, gnu compiler

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