Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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: pgconnection.cc.patch
Description: application/octet-stream (1.5 KB)
Attachment: pgconnection.h.patch
Description: application/octet-stream (395 bytes)

Responses

pgsql-bugs by date

Next:From: Robert E. BruccoleriDate: 2000-07-27 00:21:50
Subject: Re: Index selection on a large table
Previous:From: Tom LaneDate: 2000-07-26 14:27:21
Subject: Re: Index selection bug

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group