RE: User defined data types in Logical Replication - Mailing list pgsql-hackers

From Huong Dangminh
Subject RE: User defined data types in Logical Replication
Date
Msg-id 75DB81BEEA95B445AE6D576A0A5C9E936A6C3A8F@BPXM05GP.gisp.nec.co.jp
Whole thread Raw
In response to [HACKERS] User defined data types in Logical Replication  (Huong Dangminh <huo-dangminh@ys.jp.nec.com>)
Responses Re: User defined data types in Logical Replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Hi,

> We are getting the bellow error while trying use Logical Replication with
> user defined data types in a C program (when call elog function).
>
>  ERROR:  XX000: cache lookup failed for type XXXXX
>

Sorry for continuously disturbing in this topic, but am I missing something here?

I mean that in case of type's OID in PUBLICATION host does not exists in SUBSCRIPTION host's pg_type,
it could returns unintended error (the XX000 above) when elog or ereport is executed.

For more details, it happen in slot_store_error_callback when it try to call format_type_be(localtypoid) for
errcontext.
slot_store_error_callback is set in slot_store_cstrings, slot_modify_cstrings function and it also be unset here, so
theeffect here is small but it happens. 


---
Thanks and best regards,
Dang Minh Huong
NEC Solution Innovators, Ltd.
http://www.nec-solutioninnovators.co.jp/en/




pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: could not receive data from WAL stream: SSL SYSCALL error: Success
Next
From: Anthony Bykov
Date:
Subject: Re: Rewriting PL/Python's typeio code