Re: pg_rewind exiting with error code 1 when source and target are on the same timeline

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: pg_rewind exiting with error code 1 when source and target are on the same timeline
Date: 2015-10-22 05:42:20
Message-ID: CAB7nPqTZ2gnBKmNn+hzUry5Xi9=bYBoTAcMYASBnwNYH884u+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 22, 2015 at 4:08 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 10/20/15 9:31 PM, Michael Paquier wrote:
>> I have been pinged internally by a user by the fact that pg_rewind
>> returns 1 as exit code if the target and source nodes are on the same
>> timeline.
>
> I agree that that should not be an error.
> But I think in that case we should just delete that check and have the
> subsequent checks end up at the existing "no rewind required" result.

I am not sure that I am not getting completely your point, why would
it be a win to remove this safety check? We surely do not want to look
for the common ancestor timeline if the target and source nodes have
the same timeline, so we should not remove this check and just set
rewind_needed to false to fallback to the same exit(0) for all those
code paths. Per se the attached for example.
--
Michael

Attachment Content-Type Size
20151022_same_timeline_v2.patch application/x-patch 2.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2015-10-22 08:23:34 BUG #13699: float type bug
Previous Message Glenda Lewis 2015-10-22 00:57:10 PC users trying to create database