Re: Memory leak with PL/Python trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Behn, Edward (EBEHN)" <EBEHN(at)arinc(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Memory leak with PL/Python trigger
Date: 2015-11-05 18:54:45
Message-ID: 27232.1446749685@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> writes:
> Is the attached patch is in the right direction to the handle the problem?

Pretty close. Now that we've done this, we can get rid of a lot of the
retail pfree's since the memory context deletions will take care of it.
I cleaned that up a bit more and committed it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message vijaysam 2015-11-05 19:01:32 BUG #13757: Able to write to postgres even when the main process has been killed
Previous Message sdiz 2015-11-05 17:19:33 BUG #13756: jsonb_path_ops gin index produce empty result on nested array