Re: [BUG] non archived WAL removed during production crash recovery - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: [BUG] non archived WAL removed during production crash recovery
Date
Msg-id 20200402.130734.613319908534820379.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: [BUG] non archived WAL removed during production crash recovery  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: [BUG] non archived WAL removed during production crash recovery
Re: [BUG] non archived WAL removed during production crash recovery
List pgsql-bugs
Sorry, it was quite ambiguous.

At Thu, 02 Apr 2020 13:04:43 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> At Wed, 1 Apr 2020 18:17:35 +0200, Jehan-Guillaume de Rorthais <jgdr@dalibo.com> wrote in 
> > Please, find in attachment a patch implementing this.
> 
> The patch partially reintroduces the issue the patch have
> fixed. Specifically a standby running a crash recovery wrongly marks a
> WAL file as ".ready" if it is extant in pg_wal without accompanied by
> .ready file.

The patch partially reintroduces the issue the commit 78ea8b5daa have
fixed. Specifically a standby running a crash recovery wrongly marks a
WAL file as ".ready" if it is extant in pg_wal without accompanied by
.ready file.

> Perhaps checking '.ready' before the checking for archive-mode would
> be sufficient.
> 
> > Plus, I added a second commit to add one test in regard with this bug.
> > 
> > > Another is to make the startup process remove .ready file if necessary.
> > 
> > I'm not sure to understand this one.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: [BUG] non archived WAL removed during production crash recovery
Next
From: Fujii Masao
Date:
Subject: Re: [BUG] non archived WAL removed during production crash recovery