Re: could not link file in wal restore lines

From: Zsolt Ero <zsolt(dot)ero(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, michael(at)paquier(dot)xyz, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Subject: Re: could not link file in wal restore lines
Date: 2022-08-09 22:20:15
Message-ID: CAKw-smDvUWSC7sCpo7fmYGYdvAn__jXktmy+dzGp8r+Lz+H=AQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks a lot for the explanation and confirming that it's harmless.

On 10. Aug 2022 at 00:18:06, David Steele <david(at)pgmasters(dot)net> wrote:

> On 8/9/22 17:23, Zsolt Ero wrote:
>
> Can you tell me how critical is the state of this patch? I mean is there
>
> any chance of data corruption in the non-patched version?
>
>
> We believe there is no chance of corruption due to these messages.
>
> Because back-patching the better fix that was applied to PG15 could
> cause unintended consequences, our decision, at least for now, was to
> add a HINT [1] to the log message.
>
> Regards,
> -David
>
> [1]
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=41f613fc257c4d1df97f5f244461d1acb2b65227
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Maxim Boguk 2022-08-09 23:27:49 Re: BUG #17574: Attaching an invalid index to partition head make head index invalid forever
Previous Message David Steele 2022-08-09 22:18:06 Re: could not link file in wal restore lines