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

Re: pg_ctl stop -m fast

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: (view raw, whole thread or download thread mbox)
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):
	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

Next:From: Lee WuDate: 2004-10-29 16:39:13
Subject: Re: pg_restore error
Previous:From: Ivan DimitrovDate: 2004-10-29 15:54:45
Subject: Re: pg_autovacuum is not working

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