Thread

1. Libpq++ memory leak

   Michael Richards <michael@fastmail.ca> — 2000-07-26T23:42:43Z

   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

2. Re: [PATCHES] Libpq++ memory leak

   Bruce Momjian <pgman@candle.pha.pa.us> — 2000-07-27T19:43:58Z

   Applied.  Thanks.
   
   > 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, skipping... ]
   
   [ Attachment, skipping... ]
   
   
   -- 
     Bruce Momjian                        |  http://candle.pha.pa.us
     pgman@candle.pha.pa.us               |  (610) 853-3000
     +  If your life is a hard drive,     |  830 Blythe Avenue
     +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026