From: | "Lee Wu" <Lwu(at)mxlogic(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_ctl stop -m fast |
Date: | 2004-10-29 16:35:10 |
Message-ID: | ECAB83AA52BCC043A0E24BBC0000102411141F@mxhq-exch.corp.mxlogic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Tom.
May I ask in which version this bug is fixed?
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, October 28, 2004 11:10 AM
To: Lee Wu
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] pg_ctl stop -m fast
"Lee Wu" <Lwu(at)mxlogic(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Wu | 2004-10-29 16:39:13 | Re: pg_restore error |
Previous Message | Ivan Dimitrov | 2004-10-29 15:54:45 | Re: pg_autovacuum is not working |