Re: BUG #16921: small memory leak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: rekgrpth(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16921: small memory leak
Date: 2021-03-11 15:06:20
Message-ID: 2291216.1615475180@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> čt 11. 3. 2021 v 12:04 odesílatel PG Bug reporting form <
> noreply(at)postgresql(dot)org> napsal:
>> Is there a small memory leak here?
>> file: postgres/src/pl/plpgsql/src/pl_handler.c

> if I understand to source code, then it is released in function
> set_extra_field in file guc.c

Yeah, a GUC variable's "extra" storage is managed by guc.c. It
would be completely wrong for those plpgsql routines to free it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Regina Obe 2021-03-11 16:15:36 RE: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
Previous Message Tom Lane 2021-03-11 15:02:09 Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head