Re: BUG #14109: pg_rewind fails to update target control file in one scenario

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: John Lumby <johnlumby(at)hotmail(dot)com>
Cc: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, pgsql bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14109: pg_rewind fails to update target control file in one scenario
Date: 2016-04-27 00:58:45
Message-ID: CAB7nPqRoXquAKhc4605JDU0zXOxPPiwiz3DGeOYWaSN-wT45aw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Apr 27, 2016 at 9:47 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Tue, Apr 26, 2016 at 10:37 PM, John Lumby <johnlumby(at)hotmail(dot)com> wrote:
>> I did not get any answer to my suggestion in that post but I think it might be useful.
>
> Replication slots are perfectly able to retain WAL segments from a
> prior timeline, so I am not sure that this would be much a gain.

Or to put in in other words, a slot that activates automatically
itself at promotion to retain WAL from the previous timeline would be
interesting for pg_rewind, but the use case we have here is only
pg_rewind. so it seems a bit narrow to bother modifying the core core
to add this support in the replication slot code. And this can be
solved lightly with an archive. Thoughts from others are welcome.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2016-04-27 03:35:57 Re: [BUGS] Breakage with VACUUM ANALYSE + partitions
Previous Message Michael Paquier 2016-04-27 00:47:49 Re: BUG #14109: pg_rewind fails to update target control file in one scenario