Skip site navigation (1) Skip section navigation (2)

Re: pg_stop_backup does not complete

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-02-25 01:52:28
Message-ID: 16838.1267062748@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> On 2/24/10 5:36 PM, Greg Smith wrote:
>> gsmith=# select pg_stop_backup();
>> NOTICE:  pg_stop_backup cleanup done, waiting for required segments to
>> archive
>> WARNING:  pg_stop_backup still waiting for all required segments to
>> archive (60 seconds elapsed)
>> HINT:  Confirm your archive_command is executing successfully. 
>> pg_stop_backup can be aborted safely, but the resulting backup will not
>> be usable.
>> ^CCancel request sent
>> ERROR:  canceling statement due to user request

> This looks really good, thanks!

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.
Although Greg is correct that a NOTICE wouldn't be logged at default
log levels, lots of people don't use that default.  Comments?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2010-02-25 01:57:03
Subject: Re: pg_stop_backup does not complete
Previous:From: Josh BerkusDate: 2010-02-25 01:47:19
Subject: Re: pg_stop_backup does not complete

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group