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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Cade Cairns <cadec(at)otii(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1558: memory leak in libpq connectDBStart()
Date: 2005-05-07 04:23:35
Message-ID: 200505070423.j474NZS20268@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Any more information on this?

---------------------------------------------------------------------------

Cade Cairns wrote:
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John Hansen 2005-05-07 04:27:55 Re: request
Previous Message Llewellyn Falco 2005-05-07 03:41:40 request