From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ajit Awekar <ajit(dot)awekar(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Rushabh Lathia <rushabh(dot)lathia(at)enterprisedb(dot)com>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> |
Subject: | Re: Memory leak in CachememoryContext |
Date: | 2023-04-24 13:55:41 |
Message-ID: | 20230424135541.phtdpfftovykfsti@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-Apr-21, Tom Lane wrote:
> (Note to self: we can't remove the cast_hash_context field in
> back branches for fear of causing an ABI break for pldebugger.
> But we can leave it unused, I think.)
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. This seems halfway obvious, but
since the submitted patch doesn't have this part, I thought better to
point it out.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-04-24 14:09:22 | Re: run pgindent on a regular basis / scripted manner |
Previous Message | Dave Cramer | 2023-04-24 13:49:47 | Re: Request for comment on setting binary format output per session |