pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pg_ctl stop -m fast
5+ messages / 3 participants
[nested] [flat]

* pg_ctl stop -m fast
@ 2004-10-28 02:04 Lee Wu <Lwu@mxlogic.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Lee Wu @ 2004-10-28 02:04 UTC (permalink / raw)
  To: pgsql-admin-owner@postgresql.org

Hi,
 
One of our customers complains about 
pg_ctl stop -m fast
could not shutdown PG server though we cannot reproduce the same problem here.
 
They claim only "-m immediate" can take PG down after issuing "-m fast".
 
The PG version is 7.3.2.
 
What might prevent "-m fast" to shutdown PG (long transaction, etc.)?
What should I do to help the customer solve this issue?
 
Thanks,
 

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* pg_ctl stop -m fast
@ 2004-10-28 16:38 Lee Wu <Lwu@mxlogic.com>
  2004-10-28 17:10 ` Re: pg_ctl stop -m fast Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 5+ messages in thread

From: Lee Wu @ 2004-10-28 16:38 UTC (permalink / raw)
  To: pgsql-admin

Hi,

 

One of our customers complains about 

pg_ctl stop -m fast

could not shutdown PG server though we cannot reproduce the same problem
here.

 

They claim only "-m immediate" can take PG down after 10 minutes of
issuing "-m fast".

 

The PG version is 7.3.2.

 

What might prevent "-m fast" to shutdown PG (long transaction, etc.)?

What should I do to help the customer solve this issue?

 

Thanks,

 

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: pg_ctl stop -m fast
  2004-10-28 16:38 pg_ctl stop -m fast Lee Wu <Lwu@mxlogic.com>
@ 2004-10-28 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 5+ messages in thread

From: Tom Lane @ 2004-10-28 17:10 UTC (permalink / raw)
  To: Lee Wu <Lwu@mxlogic.com>; +Cc: pgsql-admin

"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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: pg_ctl stop -m fast
@ 2004-10-28 17:24 Johnson, Heather <HJohnson@nypost.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Johnson, Heather @ 2004-10-28 17:24 UTC (permalink / raw)
  To: Lee Wu <Lwu@mxlogic.com>; pgsql-admin-owner@postgresql.org; pgsql-admin

I've seen this happen. I think it happens because we have a Postgres database that is serving multiple webservers getting a high level of traffic. If you try to shut down the database while the webservers are still initiating connections to it, pg_ctl has trouble shutting it down, even with -m fast. But if you can stop the webservers from initiating new connections before you try and shut down the db, pg_ctl works fine.

Heather Johnson
Senior Database Programmer
New York Post

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
To: pgsql-admin@postgresql.org
Sent: 10/28/2004 12:38 PM
Subject: [ADMIN] pg_ctl stop -m fast

Hi,

 

One of our customers complains about 

pg_ctl stop -m fast

could not shutdown PG server though we cannot reproduce the same problem
here.

 

They claim only "-m immediate" can take PG down after 10 minutes of
issuing "-m fast".

 

The PG version is 7.3.2.

 

What might prevent "-m fast" to shutdown PG (long transaction, etc.)?

What should I do to help the customer solve this issue?

 

Thanks,

 

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: pg_ctl stop -m fast
@ 2004-10-29 16:35 Lee Wu <Lwu@mxlogic.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Lee Wu @ 2004-10-29 16:35 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: 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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2004-10-29 16:35 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-10-28 02:04 pg_ctl stop -m fast Lee Wu <Lwu@mxlogic.com>
2004-10-28 16:38 pg_ctl stop -m fast Lee Wu <Lwu@mxlogic.com>
2004-10-28 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-10-28 17:24 Re: pg_ctl stop -m fast Johnson, Heather <HJohnson@nypost.com>
2004-10-29 16:35 Re: pg_ctl stop -m fast Lee Wu <Lwu@mxlogic.com>

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