Tom Lane wrote:
> The one thing I'm undecided about is whether we want the immediate
> NOTICE, as opposed to dialing down the time till the first WARNING
> to something like 5 or 10 seconds. I think the main argument for the
> latter approach would be to avoid log-spam in normal operation
I though about that for a minute, but didn't think pg_stop_backup is a
common enough operation that anyone will complain that it's a little
more verbose in its logging now. I know when I was new to this, I used
to wonder just what it was busy doing just after executing this command
when it hung there for a while sometimes, and would have welcomed this
extra bit of detail--preferably immediately, not even after a 5 or 10
second delay.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
