Re: Log notice that checkpoint is to be written on shutdown

Hi,

Am Samstag, den 04.10.2014, 15:05 -0500 schrieb Jim Nasby:
> On 10/4/14, 1:21 PM, Jeff Janes wrote:
> > On Thu, Oct 2, 2014 at 6:21 AM, Michael Banck wrote:
> >     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?

Looking at it from a DBA perspective, this would indeed be better, yes.

However, I see a few issues with that:

1. If you are using an init script (or another wrapper around pg_ctl),
you don't get any of its output it seems.

2. Having taken a quick look at pg_ctl, it seems to just kill the
postmaster on shutdown and wait for its PID file to disappear.  I don't
see how it should figure out that PostgreSQL is waiting for a checkpoint
to be finished?