pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: rekgrpth@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16921: small memory leak
Date: Thu, 11 Mar 2021 10:06:20 -0500
Message-ID: <2291216.1615475180@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFj8pRA40V_119GVpSFuL5+hpWCY9vw2NiH_-=9quaSfUAD5Wg@mail.gmail.com>
References: <16921-23c47c8f89ba7855@postgresql.org>
	<CAFj8pRA40V_119GVpSFuL5+hpWCY9vw2NiH_-=9quaSfUAD5Wg@mail.gmail.com>

Pavel Stehule <pavel.stehule@gmail.com> writes:
> čt 11. 3. 2021 v 12:04 odesílatel PG Bug reporting form <
> noreply@postgresql.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





view thread (3+ messages)

Message-ID: <2291216.1615475180@sss.pgh.pa.us>
Permalink:  ../2291216.1615475180@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2291216.1615475180@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pavel.stehule@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16921: small memory leak
  In-Reply-To: <2291216.1615475180@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox