| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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 14:44:08 |
| Message-ID: | 193956.1682347448@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-04-24 15:10:04 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Gurjeet Singh | 2023-04-24 14:41:05 | Re: Minor code de-duplication in fe-connect.c |