Re: pg_rewind, a tool for resynchronizing an old master after failover

Поиск
Список
Период
Сортировка
От Ants Aasma
Тема Re: pg_rewind, a tool for resynchronizing an old master after failover
Дата
Msg-id CA+CSw_sGenGLFT35rBn1w+eUavEesJ+ke-iK4EyfDgWr=RWqEg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_rewind, a tool for resynchronizing an old master after failover  (Amit kapila <amit.kapila@huawei.com>)
Список pgsql-hackers
On Sat, May 25, 2013 at 10:05 AM, Amit kapila <amit.kapila@huawei.com> wrote:
>> In a nutshell, the idea is to do copy everything that has changed
>> between the cluster, like rsync does, but instead of reading through all
>> files, use the WAL to determine what has changed. Here's a somewhat more
>> detailed explanation, from the README:
>
> This is really a nice idea and an important requirement from many users.

+1

> Does this tool handle all kind of operations user would have performaed after
> forking of new cluster or it would mandate that user should not have performed certain kind of
> operations on old cluster after new cluster forked off?

Truncate and all kinds of DROP come to mind, also table rewrites from
ALTER. The tool should probably just flag those relation files to be
copied wholesale.

Regards,
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de



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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: pg_export_snapshot on standby side
Следующее
От: Simon Riggs
Дата:
Сообщение: Planning incompatibilities for Postgres 10.0