Skip site navigation (1) Skip section navigation (2)

Re: pg_ctl stop -m fast

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Lee Wu" <Lwu(at)mxlogic(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_ctl stop -m fast
Date: 2004-10-28 17:10:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"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

In response to

pgsql-admin by date

Next:From: Johnson, HeatherDate: 2004-10-28 17:24:25
Subject: Re: pg_ctl stop -m fast
Previous:From: Andrei BintintanDate: 2004-10-28 16:51:32
Subject: Re: pg_dump doesn't save correct the sequences

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group