Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master

From: Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master
Date: 2015-06-05 10:58:50
Message-ID: CAK_s-G2kZvOmdk3bOFgRgH1ciiuD7u2aMqKNRm268TzpnA0jmA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>> In addition to that change, we should make pg_basebackup skip
>> the signal file?
>
>
> Well, yes
> [...]
>
> In short, I guess that the patch attached would be fine.
> Opinions?

To me this patch seems to address the exact issue we reported and as
far as I can tell has no downside to it.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2015-06-05 14:06:47 Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master
Previous Message rajivmehta0201 2015-06-05 06:54:48 BUG #13400: Unable to connect postgresql using remote machine