Re: Memory leak with PL/Python trigger - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Memory leak with PL/Python trigger
Date
Msg-id 27232.1446749685@sss.pgh.pa.us
Whole thread Raw
In response to Re: Memory leak with PL/Python trigger  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: Memory leak with PL/Python trigger  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-bugs
Haribabu Kommi <kommi.haribabu@gmail.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

pgsql-bugs by date:

Previous
From: Breen Hagan
Date:
Subject: Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled
Next
From: vijaysam@mailworks.org
Date:
Subject: BUG #13757: Able to write to postgres even when the main process has been killed