From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_ctl inappropriately timing out? |
Date: | 2005-06-08 03:32:13 |
Message-ID: | 26627.1118201533@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)surnet(dot)cl> writes:
> On Tue, Jun 07, 2005 at 04:16:49PM -0700, Josh Berkus wrote:
>> When you call pg_ctl --stop, the WAL is still writing out to the database
>> and postmaster won't shut down until it's done, which can take a couple
>> minutes.
> Is there any way for pg_ctl to detect a "server is shutting down"
> message? Not sure what it'd do with it though ...
It strikes me that the server shouldn't ever get a couple minutes behind
on writing dirty buffers; this seems more like a bgwriter configuration
issue than pg_ctl's fault. Consider that in a standard Unix
configuration you will get about 20 seconds between SIGTERM and SIGKILL
when init wants to shut you down ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Haluk GUNCER | 2005-06-08 10:33:47 | Re: BUG #1678: pw_shadow BUS ERROR |
Previous Message | Nick Farrell | 2005-06-08 03:18:03 | BUG #1705: nextval being evaluated more than once |