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

From: Japin Li <japinli(at)hotmail(dot)com>
To: ahsan hadi <ahsan(dot)hadi(at)gmail(dot)com>
Cc: Bertrand Drouvot <bdrouvot(at)amazon(dot)com>, "Minsoo (Mike) Oh" <minsoo(at)amazon(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Date: 2021-05-08 03:17:13
Message-ID: MEYP282MB1669DE27435D7628B6D30DCBB6569@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Fri, 07 May 2021 at 19:50, ahsan hadi <ahsan(dot)hadi(at)gmail(dot)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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2021-05-08 03:26:57 Re: plan with result cache is very slow when work_mem is not enough
Previous Message Justin Pryzby 2021-05-08 02:43:20 Re: plan with result cache is very slow when work_mem is not enough