Re: pg_rewind and replication slots

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Vladimir Borodin <root(at)simply(dot)name>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_rewind and replication slots
Date: 2015-11-13 14:07:42
Message-ID: CAB7nPqTLYWwJJW_iqP3eCfwBvDw9oAAPPUDZQ4FUe53S2R71Bg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 13, 2015 at 7:41 PM, Vladimir Borodin <root(at)simply(dot)name> wrote:
> Should pg_rewind ignore pg_replslot dir at all? As it does pg_basebackup,
> for example.

To keep the code of pg_rewind simple, the decision has been made to
make pg_rewind copy everything, the necessary post-cleanup or
pre-process saving, like the target node's postgresql.conf that would
get overwritten, being at the charge of the upper application layer
calling pg_rewind.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2015-11-13 14:29:19 Re: Parallel Seq Scan
Previous Message Michael Paquier 2015-11-13 14:03:55 Re: eXtensible Transaction Manager API