Re: json_populate_record issue - TupleDesc reference leak

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: json_populate_record issue - TupleDesc reference leak
Date: 2015-05-04 14:12:30
Message-ID: 55477E4E.1060304@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 04/30/2015 08:36 AM, Pavel Stehule wrote:
> Still issue is not fixed still
>
> create type pt as (a int, b int);
> postgres=# select json_populate_record('(10,20)'::pt, '{}');
> WARNING: TupleDesc reference leak: TupleDesc 0x7f413ca325b0
> (16560,-1) still referenced
>
>

Looking at it now. (Please remember not to top-post.)

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2015-05-04 14:58:30 Re: cache invalidation for PL/pgsql functions
Previous Message Sameer Thakur 2015-05-04 12:08:39 Re: [PATCH] two-arg current_setting() with fallback