Re: pg_ctl stop -m fast - Mailing list pgsql-admin

From Lee Wu
Subject Re: pg_ctl stop -m fast
Date
Msg-id ECAB83AA52BCC043A0E24BBC0000102411141F@mxhq-exch.corp.mxlogic.com
Whole thread Raw
In response to pg_ctl stop -m fast  ("Lee Wu" <Lwu@mxlogic.com>)
List pgsql-admin
Thanks Tom.

May I ask in which version this bug is fixed?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, October 28, 2004 11:10 AM
To: Lee Wu
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_ctl stop -m fast

"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

pgsql-admin by date:

Previous
From: Ivan Dimitrov
Date:
Subject: Re: pg_autovacuum is not working
Next
From: Andy Marangakis
Date:
Subject: runaway processes, data corruption