Re: pg_stop_backup does not complete

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_stop_backup does not complete
Дата
Msg-id 16838.1267062748@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pg_stop_backup does not complete  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: pg_stop_backup does not complete  (David Fetter <david@fetter.org>)
Re: pg_stop_backup does not complete  (Greg Smith <greg@2ndquadrant.com>)
Re: pg_stop_backup does not complete  (Fujii Masao <masao.fujii@gmail.com>)
Список pgsql-hackers
Josh Berkus <josh@agliodbs.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: pg_stop_backup does not complete
Следующее
От: David Fetter
Дата:
Сообщение: Re: pg_stop_backup does not complete