Re: using an end-of-recovery record in all cases

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: sulamul(at)gmail(dot)com
Cc: robertmhaas(at)gmail(dot)com, andres(at)anarazel(dot)de, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: using an end-of-recovery record in all cases
Date: 2021-09-07 07:26:33
Message-ID: 20210907.162633.1795291481066173770.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Fri, 3 Sep 2021 15:56:35 +0530, Amul Sul <sulamul(at)gmail(dot)com> wrote in
> On Fri, Sep 3, 2021 at 10:23 AM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> You might need the following change at the end of StartupXLOG():
>
> - if (promoted)
> - RequestCheckpoint(CHECKPOINT_FORCE);
> + RequestCheckpoint(CHECKPOINT_FORCE);

At Fri, 3 Sep 2021 10:13:53 -0400, Robert Haas <robertmhaas(at)gmail(dot)com> wrote in
> Did you use the patch I posted, or a different one

Thanks to both of you. That was my stupid.

..But even with the patch (with removal of 018_..pl test file), I
didn't get check-world failed.. I'll retry later.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tanghy.fnst@fujitsu.com 2021-09-07 07:35:17 RE: [BUG] Unexpected action when publishing partition tables
Previous Message Nitin Jadhav 2021-09-07 07:24:53 Re: when the startup process doesn't (logging startup delays)