Re: pgsql: pg_rewind: Don't error if the two clusters are already on the sa

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: pg_rewind: Don't error if the two clusters are already on the sa
Date: 2015-12-12 00:11:05
Message-ID: 3796.1449879065@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> pg_rewind: Don't error if the two clusters are already on the same timeline
> This previously resulted in an error and a nonzero exit status, but
> after discussion this should rather be a noop with a zero exit status.

Hm, if we're going to do that, shouldn't we back-patch the behavior
change into 9.5 as well?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2015-12-12 01:44:14 Re: pgsql: pg_rewind: Don't error if the two clusters are already on the sa
Previous Message Tom Lane 2015-12-12 00:09:14 pgsql: Add an expected-file to match behavior of latest libxml2.

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-12-12 00:16:43 Re: Add IS (NOT) DISTINCT to subquery_Op
Previous Message Andres Freund 2015-12-11 23:55:44 Re: Bootstrap DATA is a pita