Re: BUG #14769: Logical replication error "cache lookup failed for type 0"

From: Scott Milliken <scott(at)deltaex(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14769: Logical replication error "cache lookup failed for type 0"
Date: 2017-08-08 01:31:41
Message-ID: CAM+Hv174q8wXCOUFCt7du3ByT0ZDSJcOcdFwLvUOv9Jnv1YTSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks Petr and Peter! I've tested commit and confirmed that
commit 0e58455d fixes this bug.

On Mon, Aug 7, 2017 at 7:54 AM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:

> On 8/4/17 05:41, Petr Jelinek wrote:
> >> Perhaps there's a missing check against pg_attribute.attisdropped
> >> somewhere?
> >>
> >
> > Good catch! Looks like we didn't initialize the attribute map for
> > locally dropped columns.
>
> fixed
>
> > Once I did that I found there is also typo in
> > slot_modify_cstrings() which uses wrong value from the remote side, that
> > is also made visible by your example.
>
> and fixed and added a test case
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message kyle 2017-08-08 06:09:05 BUG #14773: Incorrect documentation for the Relation logical replication message format
Previous Message Noah Misch 2017-08-08 01:06:32 Re: [BUGS] Replication to Postgres 10 on Windows is broken