Re: Memory leak with PL/Python trigger

From: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-06 09:34:05
Message-ID: CAJrrPGfENM-Rn2PdbujNNcdJodnwYaezLMnKPDKp2HSKxJyzmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs

On Fri, Nov 6, 2015 at 5:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Thank you.

Regards,
Hari Babu
Fujitsu Australia

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2015-11-06 16:06:17 Re: [HACKERS] BUG #12989: pg_size_pretty with negative values
Previous Message Michael Paquier 2015-11-06 07:47:25 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby