Re: could not link file in wal restore lines

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: david(at)pgmasters(dot)net
Cc: zsolt(dot)ero(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, michael(at)paquier(dot)xyz
Subject: Re: could not link file in wal restore lines
Date: 2022-07-26 06:03:11
Message-ID: 20220726.150311.891076428649612904.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At Tue, 26 Jul 2022 11:48:14 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Ah, sorry for posting following too-early messages in the thread.
>
> At Mon, 25 Jul 2022 08:40:12 -0400, David Steele <david(at)pgmasters(dot)net> wrote in
> > Your system seems to be doing recovery pretty quickly. I wonder if
> > there is a race condition in WAL recycling?
>
> Please take a look on [1]
>
> [1] https://www.postgresql.org/message-id/20220725.171132.2272594383346737093.horikyota.ntt%40gmail.com

And it has been fixed by cc2c7d65fc in PG15. That discussion [1]
concluded that we don't back-patch it.

regards.

[1] https://www.postgresql.org/message-id/flat/20210202151416.GB3304930%40rfd.leadboat.com
> Does anyone prefer some alternative? It's probably not worth
> back-patching anything for a restartpoint failure this rare, because
> most restartpoint outcomes are not user-visible.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Steele 2022-07-26 11:33:09 Re: could not link file in wal restore lines
Previous Message Richard Guo 2022-07-26 03:17:45 Re: BUG #17558: 15beta2: Endless loop with UNIQUE NULLS NOT DISTINCT and INSERT ... ON CONFLICT