From: | "MWendt" <marian(dot)wendt(at)inca(dot)eu> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #4510: memory leak with libpg.dll |
Date: | 2008-11-05 08:23:51 |
Message-ID: | 200811050823.mA58NpIj082798@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-11-05 10:17:12 | Re: BUG #4509: array_cat's null behaviour is inconsistent |
Previous Message | Bruce Momjian | 2008-11-05 05:02:29 | Re: Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved. |