Re: For what should pg_stop_backup wait?

Поиск
Список
Период
Сортировка
Искать
От
Simon Riggs
Тема
Re: For what should pg_stop_backup wait?
Дата
Msg-id
1218204150.4549.610.camel@ebony.2ndQuadrant
Ответ на
Список
Дерево обсуждения
For what should pg_stop_backup wait? "Fujii Masao" <masao.fujii@gmail.com>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndquadrant.com>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndquadrant.com>
Re: For what should pg_stop_backup wait? "Fujii Masao" <masao.fujii@gmail.com>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndquadrant.com>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndquadrant.com>
Re: For what should pg_stop_backup wait? Tom Lane <tgl@sss.pgh.pa.us>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndQuadrant.com>
Re: For what should pg_stop_backup wait? Tom Lane <tgl@sss.pgh.pa.us>
Re: For what should pg_stop_backup wait? Simon Riggs <simon@2ndQuadrant.com>
Re: For what should pg_stop_backup wait? "Fujii Masao" <masao.fujii@gmail.com>

On Fri, 2008-08-08 at 12:57 +0100, Simon Riggs wrote:

> > Yes, statement_timeout may help. But, I don't want to use it, because the
> > *successful* backup is canceled.
> > 
> > How about checking whether the stoppoint was archived by comparing with
> > the last WAL archived. The archiver process can tell the last WAL archived.
> > Or, we can calculate it from the status file.
> 
> I think its easier to test whether the stopxlogfilename still exists in
> pg_xlog. If not, we know it has been archived away. We can add that as
> an extra condition inside the loop.
> 
> So thinking we should test XLogArchiveCheckDone() for both
> stopxlogfilename and history file and then stat for the stop WAL file:

This seems better.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support
В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Tom Lane
Дата:
Сообщение: Re: Oprofile with postgresql
FAQ