At Fri, 29 Jul 2022 15:01:44 +0000, "Lahnov, Igor" <igor.lah...@nexign.com> wrote in > * "could not find previous WAL record at E6F/C2436F50: invalid > resource manager ID 139 at E6F/C2436F50"; or > * "could not find previous WAL record at 54E/FB348118: unexpected > pageaddr 54E/7B34A000 in log segment 000000050000054E000000FB, offset > 3448832". .. > To avoid the problem, we decided to stop using restore_command. Could you > please let us know if there is a better solution to the problem we've > described?
Perhaps almost none of us don't see what is happning there, since you didn't give us sufficient information on the configuration and exact steps. But roughly it looks like shuffling/mixing of WAL files among several systems (or WAL archives) with different histories. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
