Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns - Mailing list pgsql-hackers

From Ahsan Hadi
Subject Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Date
Msg-id CA+9bhC+ijsr4Xbt0SWGemExSZq6=j9eb+oEw7ezUZeqVH1Fuqg@mail.gmail.com
Whole thread Raw
In response to Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns  (Japin Li <japinli@hotmail.com>)
List pgsql-hackers
Tree view


On Sat, May 8, 2021 at 8:17 AM Japin Li <japinli@hotmail.com> wrote:

On Fri, 07 May 2021 at 19:50, ahsan hadi <ahsan.hadi@gmail.com> wrote:
> The following review has been posted through the commitfest application:
> make installcheck-world:  tested, passed
> Implements feature:       tested, passed
> Spec compliant:           tested, passed
> Documentation:            not tested
>
> I have also seen this error with logical replication using pglogical extension, will this patch also address similar problem with pglogical?

Does there is a test case to reproduce this problem (using pglogical)?
I encountered this, however I'm not find a case to reproduce it.

I have seen a user run into this with pglogical, the error is produced after logical decoding finds an inconsistent point. However we haven't been able to reproduce the user scenario locally...


--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.


--
Highgo Software (Canada/China/Pakistan)
URL : http://www.highgo.ca
ADDR: 10318 WHALLEY BLVD, Surrey, BC
EMAIL: mailto: ahsan.hadi@highgo.ca

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: JSON_TABLE
Next
From: Tom Lane
Date:
Subject: Reducing opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS