Horton

Re: User defined data types in Logical Replication

Masahiko Sawada <sawada.mshk@gmail.com>

View thread View on postgr.es
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: atorikoshi <torikoshi_atsushi_z2@lab.ntt.co.jp>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Huong Dangminh <huo-dangminh@ys.jp.nec.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Petr Jelinek <petr.jelinek@2ndquadrant.com>, Hiroshi Yanagisawa <hir-yanagisawa@ut.jp.nec.com>
Date: 2018-01-31T01:38:46Z
Lists: pgsql-hackers 
On Tue, Jan 30, 2018 at 6:36 PM, atorikoshi
<torikoshi_atsushi_z2@lab.ntt.co.jp> wrote:
> Hi,
>
> It seems to be in the middle of discussion, but I became a reviewer of
> this problem several days ago so I've tested the latest patch
> 'fix_slot_store_error_callback_v12.patch'.
>
> I reproduced the below ERROR by inserting elog() to INPUT function
> of CREATE TYPE, and confirmed that above patch solves the problem.
>
>>>  ERROR:  XX000: cache lookup failed for type XXXXX
>
> I also ran make check-world and there was no error.
>
> Is the only remaining topic memory leaks?
>

Yeah, but I think that the patch for the avoiding memleaks should be a
separate patch.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Commits

  1. logical replication: fix OID type mapping mechanism