Libpq++ memory leak

From: "Michael Richards" <michael(at)fastmail(dot)ca>
To: pgsql-patches(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Libpq++ memory leak
Date: 2000-07-26 23:42:43
Message-ID: 397F7773.000011.76869@frodo.searchcanada.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

Here is a bug and patch to fix it. I have tested this bug and fix on
FreeBSD/Intel and DecUX/Alpha machines. The bug appears in postgresql
6.5.3 and 7.0.2. Can someone please review it and apply it to the
source tree?

Sometimes when the postgres connection dies it is necessary to
attempt to reconnect. Calling the pgconnection::Connect method in a
derived class leaks memory because it does not clear the current
connection (if there is one). These patches ensures that any open
connections are closed before attempting to open a new one.

-Michael

Attachment Content-Type Size
pgconnection.h.patch application/octet-stream 395 bytes
pgconnection.cc.patch application/octet-stream 1.5 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andriy I Pilipenko 2000-07-27 07:38:57 Bug with 'iscachable' attribute (Was: Index selection bug)
Previous Message Tom Lane 2000-07-26 14:27:21 Re: Index selection bug

Browse pgsql-patches by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-07-27 13:37:04 some pedantic ANSI C fixes
Previous Message Michael Richards 2000-07-24 07:37:52 Patch to fix the NULL date cast bug in 7.0.2