Re: [BUG] non archived WAL removed during production crash recovery

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: jgdr(at)dalibo(dot)com
Cc: masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, michael(at)paquier(dot)xyz
Subject: Re: [BUG] non archived WAL removed during production crash recovery
Date: 2020-04-02 04:07:34
Message-ID: 20200402.130734.613319908534820379.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Sorry, it was quite ambiguous.

At Thu, 02 Apr 2020 13:04:43 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Wed, 1 Apr 2020 18:17:35 +0200, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2020-04-02 05:19:15 Re: [BUG] non archived WAL removed during production crash recovery
Previous Message Fujii Masao 2020-04-02 04:05:56 Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2020-04-02 04:13:01 Re: Proposal: Expose oldest xmin as SQL function for monitoring
Previous Message Fujii Masao 2020-04-02 04:05:56 Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)