Re: Memory leak in CachememoryContext - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leak in CachememoryContext
Date
Msg-id 312097.1682355807@sss.pgh.pa.us
Whole thread Raw
In response to Re: Memory leak in CachememoryContext  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2023-Apr-24, Tom Lane wrote:
>> 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.

> I think a session-long memory leak is not so bad, compared to a possible
> crash.  However, after looking at the code again, as well as pldebugger
> and plpgsql_check, I agree that there's no point in doing anything other
> than keeping the field there.

Yeah, I can't see any plausible reason for outside code to be using
that field (and I don't see any evidence in Debian Code Search that
anyone is).  I'll push it like this then.  Thanks for looking!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands
Next
From: Mat Arye
Date:
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames