From: | Fred Yankowski <fred(at)ontosys(dot)com> |
---|---|
To: | pgsql-cygwin(at)postgresql(dot)org |
Cc: | cygwin(at)cygwin(dot)com |
Subject: | SIGTERM does not stop backend postgres processes immediately |
Date: | 2001-05-08 19:24:27 |
Message-ID: | 20010508142427.A25541@enteract.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
It seems that postgres backend processes built with Cygwin do not
react to the SIGTERM signal immediately. Instead, they remain blocked
on a recv() call deep under ReadCommand() and don't notice the signal
until data comes in over the socket connection and unblocks recv().
This prevents a 'fast' stop of the whole PostgreSQL instance from
working correctly.
I'm seeing this problem in Cygwin 1.3.1 with cygipc-1.09-2, using
PostgreSQL built from source based on a very recent CVS snapshot.
This problem sounds similar to one reported in the pgsql-ports list
earlier this year [1]. That thread concludes that it's a Cygwin
problem, but with no solution yet. Has there been any progress since
then?
[1] http://postgresql.readysetnet.com/mhonarc/pgsql-ports/2001-01/msg00023.html
--
Fred Yankowski fred(at)OntoSys(dot)com tel: +1.630.879.1312
Principal Consultant www.OntoSys.com fax: +1.630.879.1370
OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA
From | Date | Subject | |
---|---|---|---|
Next Message | adez | 2001-05-09 01:26:47 | about why build again |
Previous Message | Jason Tishler | 2001-05-08 12:26:12 | Re: Port problem PostgreSQL to WinNT/2000 |