Horton

Re: Memory leak in CachememoryContext

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Ajit Awekar <ajit.awekar@enterprisedb.com>, pgsql-hackers@lists.postgresql.org, Rushabh Lathia <rushabh.lathia@enterprisedb.com>, Jeevan Chalke <jeevan.chalke@enterprisedb.com>
Date: 2023-04-24T14:44:08Z
Lists: pgsql-hackers 
I wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>> Hmm, we can leave it unused in our code, but it still needs to be
>> initialized to some valid memory context anyway; otherwise hypothetical
>> code that uses it would still crash.

> I think we want that to happen, actually, because it's impossible
> to guess what such hypothetical code needs the context to be.

I guess we could have the back branches continue to create a
shared_cast_context and just not use it in core.  Seems rather
expensive for a very hypothetical compatibility measure, though.

			regards, tom lane

Commits

  1. Fix memory leakage in plpgsql DO blocks that use cast expressions.