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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, scott(at)deltaex(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14769: Logical replication error "cache lookup failed for type 0"
Date: 2017-08-07 14:54:13
Message-ID: ec84927a-6e4a-8452-33ad-43b9a8552879@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2017-08-07 15:17:20 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Previous Message Fabien COELHO 2017-08-07 14:32:39 Re: BUG #14772: psql autocommit does not work