Re: Reference Leak with type

On Tue, Apr 06, 2021 at 11:09:13AM +0530, Rohit Bhogate wrote:
>  I found the below reference leak on master.

Thanks for the report.  This is indeed a new problem as of HEAD,
coming from c9d52984 as far as I can see, and 13 does not support this
grammar.  From what I can see, there seems to be an issue with the
reference count of the TupleDesc here, your test case increments two
times a TupleDesc for this custom type in a portal, and tries to
decrement it three times, causing what looks like a leak.
--
Michael