| From: | Zsolt Ero <zsolt(dot)ero(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | david(at)pgmasters(dot)net, 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-08-09 21:23:31 |
| Message-ID: | CAKw-smDWZj5u=kYW0Rkbn7-iEn9NAxODwRYgN1SwmauAuDF-gA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
Zsolt
On 27. Jul 2022 at 04:52:31, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
wrote:
> I'm gonig to modify the patch for PG12 then come up again.
>
>
> So, this is the version of cc2c7d65fc that is minimally modified (but
> not checked seriously) for PG12. (cc2c7d65fc was almost cleanly
> applied.)
>
> I applied this and observed that WAL recycleing is prevented until
> archive recovery ends and I finally didn't see the "could not link"
> error happen.
>
> Zsolt, could you confirm this patch works for you?
>
> regards
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2022-08-09 22:18:06 | Re: could not link file in wal restore lines |
| Previous Message | Svante Richter | 2022-08-09 20:48:56 | Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV |