From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | MWendt <marian(dot)wendt(at)inca(dot)eu> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4510: memory leak with libpg.dll |
Date: | 2008-11-05 11:15:45 |
Message-ID: | 49118061.1010401@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
MWendt wrote:
> The following bug has been logged online:
>
> Bug reference: 4510
> Logged by: MWendt
> Email address: marian(dot)wendt(at)inca(dot)eu
> PostgreSQL version: 8.1.x, 8.2.x
> Operating system: windows xp (client), linux (postgres server)
> Description: memory leak with libpg.dll
> Details:
>
> 1) DB server is down.
> 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. and furthermore the memory is
> not freed when the next connection can be established.
> 3) I guess in libpg.dll are some connection structures that are not freed
> correctly if the connection coult not established well.
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.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2008-11-05 14:06:10 | Re: [ODBC] Behavior change of FK info query |
Previous Message | Peter Eisentraut | 2008-11-05 10:17:12 | Re: BUG #4509: array_cat's null behaviour is inconsistent |