Re: BUG #15346: Replica fails to start after the crash

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: cyberdemn(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, alvherre(at)2ndquadrant(dot)com, 9erthalion6(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15346: Replica fails to start after the crash
Date: 2018-08-31 18:10:08
Message-ID: 20180831181008.GB5305@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Aug 30, 2018 at 11:23:54PM -0700, Michael Paquier wrote:
> Yes that's a matter of safety, as I put into the truck any modules which
> may use XLogFlush(). And that maps with the old code, so there is no
> more surprise.

Okay, I have pushed my previous version as that's the safest approach.
If you have any idea of improvements or clarifications, let's discuss
about those on a different thread and only for HEAD.

Many thanks Alexander for the whole work and Horiguchi-san for the
review.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message jhm713 2018-08-31 19:22:58 Re: Inconsistencies restoring public schema ownership from pg_dump
Previous Message Andrew Gierth 2018-08-31 09:51:00 Re: BUG #15352: postgresql FDW error "ERROR: ORDER BY position 0 is not in select list"

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-08-31 18:46:47 Re: Bug in slot.c and are replication slots ever used at Window?
Previous Message Michael Paquier 2018-08-31 17:27:16 Re: Negotiating the SCRAM channel binding type