From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Superuser connect during smart shutdown |
Date: | 2014-10-17 03:16:05 |
Message-ID: | 544089F5.4090204@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/17/2014 03:59 AM, Jim Nasby wrote:
> Over in the "Log notice that checkpoint is to be written on shutdown"
> thread...
>
> On 10/16/14, 2:31 PM, Michael Banck wrote:
>> There were some comments that this might not actually be the case and/or
>> that the postmaster was simply waiting for clients to disconnect due to
>> smart shutdown being invoked.
>
> Something else mentioned was that once you start a smart shutdown you
> have no good way (other than limited ps output) to see what the shutdown
> is waiting on. I'd like to have some way to get back into the database
> to see what's going on. Perhaps we could allow superusers to connect
> while waiting for shutdown. A big warning that we're in shutdown would
> be nice, and maybe it would make sense to further restrict this to only
> local connections.
You'd also want to flag this connection so it's ignored by the smart
shutdown check, allowing the server to shut down even if it's active.
That'd be a pretty useful thing to have anyway, so monitoring tools,
long-running reports that can be restarted ,etc can mark their
connections as ignored for the purpose of smart shutdown.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-10-17 03:34:51 | [PATCH] HINT: pg_hba.conf changed since last config reload |
Previous Message | Caleb Welton | 2014-10-17 01:21:01 | Issue with mkdtemp() in port.h |