Re: BUG #4510: memory leak with libpg.dll - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4510: memory leak with libpg.dll
Date
Msg-id 14492.1225899196@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #4510: memory leak with libpg.dll  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-bugs
Craig Ringer <craig@postnewspapers.com.au> writes:
> MWendt wrote:
>> 2) the client will connect to these DB server and is running correctly in a
>> timeout. the problem is: for each connection attempt that will fail the
>> memory usage is growing. that will result in massive memory allocation, if
>> the client try to reconnect in high frequency.

> Is there any chance you can supply the source code of a self-contained,
> compileable test case (example program) that can demonstrate this? Your
> description doesn't exclude the possibility of leaks occurring as a
> consequence of failure to free resources in the program using libpq.

In particular I wonder whether the application is neglecting to call
PQfinish() on the failed connection objects ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Jeff
Date:
Subject: Re: plperl & sort
Next
From: Tom Lane
Date:
Subject: Re: BUG #4509: array_cat's null behaviour is inconsistent