Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lfS3c-0003HQ-U4 for pgsql-hackers@arkaria.postgresql.org; Sat, 08 May 2021 18:52:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lfS3a-0003vm-9E for pgsql-hackers@arkaria.postgresql.org; Sat, 08 May 2021 18:52:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lfS3Z-0003ve-Un for pgsql-hackers@lists.postgresql.org; Sat, 08 May 2021 18:52:06 +0000 Received: from mail-yb1-xb29.google.com ([2607:f8b0:4864:20::b29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lfS3T-0003b8-2Z for pgsql-hackers@lists.postgresql.org; Sat, 08 May 2021 18:52:05 +0000 Received: by mail-yb1-xb29.google.com with SMTP id r8so16253070ybb.9 for ; Sat, 08 May 2021 11:51:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0K573XnvAd1ezUcfzTXmjknQguz3c2nWSwG+os16n8M=; b=pUt+EAuCYbQ2qJj9PJgFRYTp7PsyKpuGoktpFqTBlts+ZFmOeTmWCJJAa+aDWztZuN vj3gsjrWXobbTiaTf9Pwyk5iPJbQTHLRx9pJIxIGGLeHw4NZCmdB6ygLBZesaq41qrXl 2BzssH927XqL9yhsOQbMlfJa38K1ovhu9x1uw4dsjlcA4Eldp2Cm3YFCYe81qgXVWy3V DU8oMjKT2dROWwZcgbn+S82dL9rulmv8EJG4z2pd4oQyR++zooF4mr6Nwo0AY5H8GPLt 2RchyuSyQiOP2+zXS4MiE+ujLjekCurY0GayOgVj2Pz3ARz30D81nEqfP8dvvO1bM4XS FsNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0K573XnvAd1ezUcfzTXmjknQguz3c2nWSwG+os16n8M=; b=PV1sr1pk/mS2hOfm2bE98sPAqQA1s3Wd1nDnDoDHG6GKoJyjcwApZkh6oKu7FIHusZ 71ts5iQ+tug0t0Fc5/EA26FlJYPugmIRKQabUstAv62fP0+dwCqP0toMXbOiujrIgUYr hF4umgB9UWwe0722oA16+mYcn/Mm2LjHlO2OXZIW32Z6RbA5z/KCGzVu6aMB2mbEgD4v 3iO8qkZXNK1AgtlqqnETuWG7iyNm7iqLbhu7EGMPFDcwa2vEOXGTfDKb0l2JI2+SspDr +TtN8zAcMPpPnYwSJzMpVTy7WhxKatITeSrJ31ZF2B3o9dGpiomngf4VMNkFFaCxkD9h d9Dg== X-Gm-Message-State: AOAM531AyJ9GPvmk5F7ZyQ09mGEFJKjqJ6JQ/PK293HpMQC0Jm5ULjlU wYuvk0/bvwV0VxPUPx2l0KIcXUAiHMDtwSsrM3M= X-Google-Smtp-Source: ABdhPJwcEXvZ21qj0B018+vFgSjAFbBPeDCRe9OB5lD90J8Bmhp4FrHBt/htpAU2wWgznTvup729R20bBZZFaRPLVoQ= X-Received: by 2002:a25:3585:: with SMTP id c127mr22832080yba.494.1620499917052; Sat, 08 May 2021 11:51:57 -0700 (PDT) MIME-Version: 1.0 References: <81D0D8B0-E7C4-4999-B616-1E5004DBDCD2@amazon.com> <162038822425.16755.16394090984207683374.pgcf@coridan.postgresql.org> In-Reply-To: From: Ahsan Hadi Date: Sat, 8 May 2021 23:51:45 +0500 Message-ID: Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns To: Japin Li Cc: Bertrand Drouvot , "Minsoo (Mike) Oh" , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="000000000000ea1dd505c1d6099f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ea1dd505c1d6099f Content-Type: text/plain; charset="UTF-8" On Sat, May 8, 2021 at 8:17 AM Japin Li wrote: > > On Fri, 07 May 2021 at 19:50, ahsan hadi 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 --000000000000ea1dd505c1d6099f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

On Fri, 07 May 2021 at 19:50, ahsan hadi <ahsan.hadi@gmail.com> wrote:
> The following review has been posted through the commitfest applicatio= n:
> make installcheck-world:=C2=A0 tested, passed
> Implements feature:=C2=A0 =C2=A0 =C2=A0 =C2=A0tested, passed
> Spec compliant:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0tested, passed=
> Documentation:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 not tested
>
> I have also seen this error with logical replication using pglogical e= xtension, 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 pglogic= al, the error is produced after logical decoding finds an inconsistent poin= t. 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 :=C2=A0http://www.highgo.ca
ADDR: 10318 WHALLEY BLVD, Surre= y, BC
= EMAIL: mai= lto:=C2=A0ahsan.hadi@highgo.ca
--000000000000ea1dd505c1d6099f--