Re: Remove non-fast promotion Re: Should we remove a fallback promotion? take 2

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: andres(at)anarazel(dot)de, alvherre(at)2ndquadrant(dot)com, michael(at)paquier(dot)xyz, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Remove non-fast promotion Re: Should we remove a fallback promotion? take 2
Date: 2020-04-21 13:08:56
Message-ID: c85599fe-859e-308a-2393-6c1c4f533117@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/04/21 17:15, Kyotaro Horiguchi wrote:
> At Mon, 20 Apr 2020 15:26:16 +0900, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote in
>> Patch attached. I will add this into the first CF for v14.
>
> - if (!fast_promoted)
> + if (!promoted)
> RequestCheckpoint(CHECKPOINT_END_OF_RECOVERY |
> CHECKPOINT_IMMEDIATE |
> CHECKPOINT_WAIT);
>
> If we don't find the checkpoint record just before, we don't insert
> End-Of-Recovery record then run an immediate chekpoint. I think if we
> nuke the non-fast promotion, shouldn't we insert the EOR record even
> in that case?

I'm not sure if that's safe. What if the server crashes before the checkpoint
completes in that case? Since the last checkpoint record is not available,
the subsequent crash recovery will fail. This would lead to that the server
will never start up. Right? Currently ISTM that end-of-recovery-checkpoint
is executed to avoid such trouble in that case.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Dude 2020-04-21 13:48:09 [SSPI] Windows group support
Previous Message Juan José Santamaría Flecha 2020-04-21 12:49:41 Re: PG compilation error with Visual Studio 2015/2017/2019