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

From atorikoshi
Subject Re: User defined data types in Logical Replication
Date
Msg-id cfdf8f05-f031-c8c2-3711-af0c626a3a8d@lab.ntt.co.jp
Whole thread Raw
In response to Re: User defined data types in Logical Replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: User defined data types in Logical Replication
List pgsql-hackers
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?


On 2018/01/09 17:22, Masahiko Sawada wrote:

 >> I suppose it's not a common use pattern, but it'd be good
 >> to avoid everlasting memleaks.
 >
 > I agree. Can we remove entry from hash table in the callbacks instead
 > of setting InvalidOid when invalidate caches?


-- 
Atsushi Torikoshi
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Alexander Kuzmenkov
Date:
Subject: Re: [HACKERS] PoC: full merge join on comparison clause
Next
From: Amit Langote
Date:
Subject: Re: non-bulk inserts and tuple routing