Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E07219F9E6D; Mon, 3 Sep 2007 10:42:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 08207-02; Mon, 3 Sep 2007 10:42:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DF0C99F9F2F; Mon, 3 Sep 2007 10:42:25 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l83DgLvj007895; Mon, 3 Sep 2007 09:42:21 -0400 (EDT) To: "Scott Marlowe" cc: "Anoo Sivadasan Pillai" , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: FW: max_connections and shared_buffers In-reply-to: References: <772CDA49C515244FA14E34443F62E56402F173E0@EX-INDIA1.internal.rmplc.net> <772CDA49C515244FA14E34443F62E56402F17455@EX-INDIA1.internal.rmplc.net> Comments: In-reply-to "Scott Marlowe" message dated "Mon, 03 Sep 2007 02:28:11 -0500" Date: Mon, 03 Sep 2007 09:42:21 -0400 Message-ID: <7894.1188826941@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/13 X-Sequence-Number: 26774 "Scott Marlowe" writes: > Not sure with Windows. I'm strictly a unix type of guy. I'm guessing > that Windows is detecting too many connections / out of memory and > shutting down the service. The whole thing is pretty strange. "received fast shutdown request" means that the postmaster got SIGINT --- a moment's look at the code proves there is no other possibility. Now what sent it SIGINT? AFAICS there are only two possible paths: "pg_ctl stop -m fast" or this little bit of code in win32/signal.c: /* Console control handler will execute on a thread created by the OS at the time of invocation */ static BOOL WINAPI pg_console_handler(DWORD dwCtrlType) { if (dwCtrlType == CTRL_C_EVENT || dwCtrlType == CTRL_BREAK_EVENT || dwCtrlType == CTRL_CLOSE_EVENT || dwCtrlType == CTRL_SHUTDOWN_EVENT) { pg_queue_signal(SIGINT); return TRUE; } return FALSE; } Can any Windows hackers speculate on causes of this? regards, tom lane