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

From osumi.takamichi@fujitsu.com
Subject RE: Stronger safeguard for archive recovery not to miss data
Date
Msg-id OSBPR01MB48887EFFCA39FA9B1DBAFB0FEDBD0@OSBPR01MB4888.jpnprd01.prod.outlook.com
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  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
Hi


On Monday, January 25, 2021 5:13 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> 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.
Updated. This patch showed no failure during regression tests
and has been aligned by pgindent.

Best Regards,
    Takamichi Osumi


Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies
Next
From: "k.jamison@fujitsu.com"
Date:
Subject: RE: libpq debug log