From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | zsolt(dot)ero(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-07-27 02:52:31 |
Message-ID: | 20220727.115231.2253693006154033555.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> 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
Attachment | Content-Type | Size |
---|---|---|
cc2c7d65fc_for_PG12.patch | text/x-patch | 39 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2022-07-27 07:32:46 | BUG #17559: Inconsistent visibility in trigger function |
Previous Message | Kyotaro Horiguchi | 2022-07-27 02:15:20 | Re: could not link file in wal restore lines |