Horton

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>

View thread View on postgr.es
From: Ahsan Hadi <ahsan.hadi@gmail.com>
To: Japin Li <japinli@hotmail.com>
Cc: Bertrand Drouvot <bdrouvot@amazon.com>, "Minsoo (Mike) Oh" <minsoo@amazon.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-08T18:51:45Z
Lists: pgsql-hackers 
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

Commits

  1. Fix the incorrect assertion introduced in commit 7f13ac8123.

  2. Fix catalog lookup with the wrong snapshot during logical decoding.

  3. Clean up assorted failures under clang's -fsanitize=undefined checks.