Re: Collection of memory leaks for ECPG driver

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>
Subject: Re: Collection of memory leaks for ECPG driver
Date: 2015-06-16 00:06:40
Message-ID: CAB7nPqTZvYM6Uzp481SJNixbpAi76=-5iUFrYax3ZJVOmS=iSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 15, 2015 at 9:33 PM, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> On Sun, Jun 14, 2015 at 08:43:13PM +0900, Michael Paquier wrote:
>> point out that there is still a leak in connect.c. Per se the attached
>> patch, that does not check for a NULL pointer before ecpg_free because
>> other code paths in the routine patched don't do so. So you get
>> something locally consistent ;)
>
> Thanks, committed.

Thanks.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-06-16 00:26:26 Re: Need Multixact Freezing Docs
Previous Message Brendan Jurd 2015-06-16 00:04:18 Re: Function to get size of notification queue?