From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Michael Banck <michael(dot)banck(at)credativ(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Log notice that checkpoint is to be written on shutdown |
Date: | 2014-10-04 20:05:02 |
Message-ID: | 543052EE.9000506@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/4/14, 1:21 PM, Jeff Janes wrote:
> On Thu, Oct 2, 2014 at 6:21 AM, Michael Banck <michael(dot)banck(at)credativ(dot)de <mailto:michael(dot)banck(at)credativ(dot)de>> wrote:
>
> Hi,
>
> we have seen repeatedly that users can be confused about why PostgreSQL
> is not shutting down even though they requested it. Usually, this is
> because `log_checkpoints' is not enabled and the final checkpoint is
> being written, delaying shutdown. As no message besides "shutting down"
> is written to the server log in this case, we even had users believing
> the server was hanging and pondering killing it manually.
>
>
> Wouldn't a better place to write this message be the terminal from which "pg_ctl stop" was invoked, rather than the server log file?
>
+1
Or do both. I suspect elog( INFO, ... ) might do that.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-10-04 20:13:30 | Re: Replication identifiers, take 3 |
Previous Message | Jim Nasby | 2014-10-04 20:01:45 | Re: Aussie timezone database changes incoming |