| From: | Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | Bertrand Drouvot <bdrouvot(at)amazon(dot)com>, "Minsoo (Mike) Oh" <minsoo(at)amazon(dot)com>, PostgreSQL Hackers <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 18:51:45 |
| Message-ID: | CA+9bhC+ijsr4Xbt0SWGemExSZq6=j9eb+oEw7ezUZeqVH1Fuqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 8, 2021 at 8:17 AM Japin Li <japinli(at)hotmail(dot)com> wrote:
>
> 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.
>
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(dot)hadi(at)highgo(dot)ca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-05-08 19:44:57 | Reducing opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS |
| Previous Message | Andrew Dunstan | 2021-05-08 18:23:32 | Re: SQL/JSON: JSON_TABLE |