Re: Forcing current WAL file to be archived

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: Forcing current WAL file to be archived
Дата
Msg-id 20060725155851.GM20016@kenobi.snowman.net
обсуждение исходный текст
Ответ на Re: Forcing current WAL file to be archived  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-hackers
* Simon Riggs (simon@2ndquadrant.com) wrote:
> On Tue, 2006-07-25 at 11:20 -0400, Bruce Momjian wrote:
> > Yes, perhaps, though I can envision a GUC that does regularly partial
> > archiving.  I will add a question mark to the item.
>
> I was planning to add a new GUC
>
>     archive_timeout (integer) = max # secs between log file switches

I'd love to see both this GUC and the function itself make it into 8.2..

I'm tempted to agree with Bruce about running the wal-archive-function
after pg_stop_backup().  The backup isn't any good without all the WALs
which were used during the backup anyway (iirc) so I can't really think
why you'd want any time at all between "backup happening" and "backup
actually usable".

Also, compared to the backup itself I'd tend to doubt there would be
much of a performance hit.  It may be expensive compared to other
regular queries/operations but an rsync across the entire database isn't
exactly cheap.
Thanks,
    Stephen

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Forcing current WAL file to be archived
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Forcing current WAL file to be archived