Re: BUG #1558: memory leak in libpq connectDBStart()

From: Cade Cairns <cadec(at)otii(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1558: memory leak in libpq connectDBStart()
Date: 2005-03-28 04:34:34
Message-ID: b9898e36a2684665f8a0cdbbc7d7c2c5@otii.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I will post a patch in a few days. I am extremely busy and don't have
adequate time. I apologize for not having posted more in the first
place.

On 27-Mar-05, at 1:12 AM, Tom Lane wrote:

> "Cade Cairns" <cadec(at)otii(dot)com> writes:
>> The leak occurs when libpq can not establish a connection to the
>> database
>> server, in my case when it is not running. I believe that when a
>> caller
>> calls PQreset() or PQresetStart(), the subsequent call to
>> connectDBStart()
>> clobbers the previous value of addrlist in the PGconn. Presumably,
>> closePGconn() should be destroying this value.
>
> Uh ... could we see a complete test case for this?
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2005-03-28 05:02:51 Re: can install pg - it's unbelievable
Previous Message John Smith 2005-03-28 00:51:42 Re: BUG #1547: CREATE TYPE AS error