Re: archive status ".ready" files may be created too early

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "matsumura(dot)ryo(at)fujitsu(dot)com" <matsumura(dot)ryo(at)fujitsu(dot)com>
Cc: 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com>, "bossartn(at)amazon(dot)com" <bossartn(at)amazon(dot)com>, "masao(dot)fujii(at)gmail(dot)com" <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: archive status ".ready" files may be created too early
Date: 2020-09-07 03:07:16
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Wed, Jul 22, 2020 at 02:53:49AM +0000, matsumura(dot)ryo(at)fujitsu(dot)com wrote:
> Then, Record-A may be invalidated by crash-recovery and overwritten by new WAL record.
> The segment-X is not same as the archived one.

Please note that the latest patch fails to apply per the CF bot, so a
rebase would be in order to have at least some automated tests for the
last patch.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-09-07 03:10:37 Re: [PATCH] audo-detect and use -moutline-atomics compilation flag for aarch64
Previous Message Michael Paquier 2020-09-07 03:05:26 Re: vacuum verbose: show pages marked allvisible/frozen/hintbits