Re: BUG #4510: memory leak with libpg.dll

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: MWendt <marian(dot)wendt(at)inca(dot)eu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4510: memory leak with libpg.dll
Date: 2008-11-05 15:33:16
Message-ID: 14492.1225899196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Craig Ringer <craig(at)postnewspapers(dot)com(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-11-05 16:03:40 Re: BUG #4509: array_cat's null behaviour is inconsistent
Previous Message Jeff 2008-11-05 14:16:26 Re: plperl & sort