Re: BUG #1558: memory leak in libpq connectDBStart() - Mailing list pgsql-bugs

From Cade Cairns
Subject Re: BUG #1558: memory leak in libpq connectDBStart()
Date
Msg-id b9898e36a2684665f8a0cdbbc7d7c2c5@otii.com
Whole thread Raw
In response to Re: BUG #1558: memory leak in libpq connectDBStart()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1558: memory leak in libpq connectDBStart()
List 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@otii.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

pgsql-bugs by date:

Previous
From: "John Smith"
Date:
Subject: Re: BUG #1547: CREATE TYPE AS error
Next
From: Tom Lane
Date:
Subject: Re: BUG in pg_autovacuum - with patch