X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1872C3A491D for ; Thu, 28 Oct 2004 18:10:34 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 67851-08 for ; Thu, 28 Oct 2004 17:10:24 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 01D153A494C for ; Thu, 28 Oct 2004 18:10:24 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9SHAKlM003160; Thu, 28 Oct 2004 13:10:20 -0400 (EDT) To: "Lee Wu" Cc: pgsql-admin@postgresql.org Subject: Re: pg_ctl stop -m fast In-reply-to: References: Comments: In-reply-to "Lee Wu" message dated "Thu, 28 Oct 2004 10:38:28 -0600" Date: Thu, 28 Oct 2004 13:10:20 -0400 Message-ID: <3159.1098983420@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/366 X-Sequence-Number: 15359 "Lee Wu" writes: > They claim only "-m immediate" can take PG down after 10 minutes of > issuing "-m fast". > The PG version is 7.3.2. This is a known bug in 7.3.2 and before, if there is an idle backend that hasn't received any user query since it got a SIGUSR2 interrupt. 2003-02-17 21:53 tgl * src/backend/commands/async.c (REL7_3_STABLE): Async_NotifyHandler must save and restore ImmediateInterruptOK. Fixes known problem with failure to respond to 'pg_ctl stop -m fast', and probable problems if SIGINT or SIGTERM arrives while processing a SIGUSR2 interrupt that arrived while waiting for a new client query. regards, tom lane