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 Japin Li
Subject Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Date
Msg-id MEYP282MB1669DE27435D7628B6D30DCBB6569@MEYP282MB1669.AUSP282.PROD.OUTLOOK.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  (ahsan hadi <ahsan.hadi@gmail.com>)
Responses Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
List pgsql-hackers
Tree view 
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
problemwith 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.

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

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: plan with result cache is very slow when work_mem is not enough
Next
From: David Rowley
Date:
Subject: Re: plan with result cache is very slow when work_mem is not enough