Re: Stronger safeguard for archive recovery not to miss data - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Stronger safeguard for archive recovery not to miss data
Date
Msg-id 3d982f60ba2c897131dccc7111ae05ca40b33d0a.camel@cybertec.at
Whole thread Raw
In response to Re: Stronger safeguard for archive recovery not to miss data  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses RE: Stronger safeguard for archive recovery not to miss data  ("osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>)
List pgsql-hackers
On Thu, 2021-01-21 at 15:30 +0100, I wrote:
> On Thu, 2021-01-21 at 13:09 +0000, osumi.takamichi@fujitsu.com wrote:
> 
> > > My vote is that we should not have a GUC for such an unlikely event, and that
> > > stopping recovery is good enough.
> > OK. IIUC, my current patch for this fix doesn't need to be changed or withdrawn.
> > Thank you for your explanation.
> 
> Well, that's just my opinion.
> 
> Fujii Masao seemed to disagree with the patch, and his voice carries weight.

I think you should pst another patch where the second, now superfluous,
error message is removed.

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Mark Rofail
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Mark Rofail
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays