From: | johann at 2ndquadrant(dot)com (Johann 'Myrkraverk' Oskarsson) |
---|---|
To: | |
Subject: | [Pljava-dev] TupleDesc reference leak |
Date: | 2012-06-21 10:51:46 |
Message-ID: | um3k9z.x5um3k9z.8vfh.ued9.gnus@asuka.myrkraverk.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
Hi Heikki,
Heikki Linnakangas <heikki.linnakangas at enterprisedb.com> writes:
> The other is in Type.c, in Type_fromOid function:
> I'm not sure what to do about that one. UDT_registerUDT() puts the
> TupleDesc Reference to a field in the UDT instance it creates. It's
> not clear to me what the lifecycle of that instance is. If we just
> created a copy of the TupleDesc, would we leak memory? Can the UDT
> object persist over transactions, in which case it holds a dangling
> pointer to the TupleDesc?
I'll have to take a closer look at that later. Hence I have not closed
the bug.
> Anyway, please apply the attached patch, at least.
Done. Thank you.
--
Johann Oskarsson http://www.2ndquadrant.com/ |[]
PostgreSQL Development, 24x7 Support, Training and Services --+--
|
Blog: http://my.opera.com/myrkraverk/blog/
From | Date | Subject | |
---|---|---|---|
Next Message | Johann 'Myrkraverk' Oskarsson | 2012-06-21 22:25:00 | [Pljava-dev] Blog: Performing SQL with PL/Java in PostgreSQL |
Previous Message | Heikki Linnakangas | 2012-06-21 06:52:31 | [Pljava-dev] TupleDesc reference leak |