Re: Fast or immediate shutdown

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fast or immediate shutdown
Date: 2009-12-16 15:42:13
Message-ID: 1260978133.634.1569.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2009-12-16 at 17:04 +0200, Peter Eisentraut wrote:
> On tis, 2009-12-15 at 17:19 +0000, Simon Riggs wrote:
> > running with log_checkpoints = on
> >
> > pg_ctl -D foo -m fast stop
> >
> > log says
> >
> > LOG: received fast shutdown request
> > LOG: aborting any active transactions
> > LOG: shutting down
> > LOG: restartpoint starting: shutdown immediate
> >
> > Some of us know that the "immediate" word refers to the restartpoint
> > request, though that word causes conceptual conflict with the shutdown
> > mode, which was fast, not immediate.
> >
> > Think we need to change the wording of this
> >
> > LOG: restartpoint starting: shutdown immediate
> >
> > so it is clearer what we mean
>
> We *do* we mean? And why are we logging it?

The words after the colon refer to options sent to RequestCheckpoint and
it is logged because we asked for it by doing log_checkpoints = on.

I suggest we say "smoothed" when checkpoint option is !immediate. So we
will remove the word "immediate" from the message.

--
Simon Riggs www.2ndQuadrant.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kurt Harriman 2009-12-16 15:44:50 PostgreSQL project policy compendium
Previous Message Pavel Stehule 2009-12-16 15:42:07 Re: idea - new aggregates median, listagg