| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | atorikoshi <torikoshi_atsushi_z2(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Hiroshi Yanagisawa <hir-yanagisawa(at)ut(dot)jp(dot)nec(dot)com> |
| Subject: | Re: User defined data types in Logical Replication |
| Date: | 2018-01-31 01:38:46 |
| Message-ID: | CAD21AoCNC3oBbEBw0mEpAT2rUiLhTcUE9+8V25MO=p5T8vjkUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 30, 2018 at 6:36 PM, atorikoshi
<torikoshi_atsushi_z2(at)lab(dot)ntt(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-01-31 01:42:26 | Re: JIT compiling with LLVM v9.0 |
| Previous Message | Amit Langote | 2018-01-31 00:50:50 | Re: [Sender Address Forgery]Re: FOR EACH ROW triggers on partitioned tables |