From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lee Wu <Lwu@mxlogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_ctl stop -m fast
Date: Thu, 28 Oct 2004 13:10:20 -0400
Message-ID: <3159.1098983420@sss.pgh.pa.us> (raw)
In-Reply-To: <ECAB83AA52BCC043A0E24BBC0000102411141B@mxhq-exch.corp.mxlogic.com>
References: <ECAB83AA52BCC043A0E24BBC0000102411141B@mxhq-exch.corp.mxlogic.com>
"Lee Wu" <Lwu@mxlogic.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Lwu@mxlogic.com
Subject: Re: pg_ctl stop -m fast
In-Reply-To: <3159.1098983420@sss.pgh.pa.us>
References: <ECAB83AA52BCC043A0E24BBC0000102411141B@mxhq-exch.corp.mxlogic.com> <3159.1098983420@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox