Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id UAA68809 for ; Mon, 17 Apr 2000 20:51:46 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id UAA16486; Mon, 17 Apr 2000 20:51:32 -0400 (EDT) To: Tim Brookes cc: pgsql-interfaces@postgresql.org Subject: Re: libpq++ memory problems In-reply-to: <38FB6FA1.C63B030B@mcmail.com> References: <38FB6FA1.C63B030B@mcmail.com> Comments: In-reply-to Tim Brookes message dated "Mon, 17 Apr 2000 21:10:09 +0100" Date: Mon, 17 Apr 2000 20:51:32 -0400 Message-ID: <16483.956019092@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/108 Tim Brookes writes: > The procedure 'callproc' is called in a continuous loop to emphasise > this problem. Within the procedure all that happens is a new database > connection is made and deleted. On my system this eats memory at an > enormous rate. I could not reproduce such a leak with current sources. It appears that you are using a fairly old Postgres release --- class PgEnv hasn't existed since at least release 6.4.*, maybe earlier. I'd suggest upgrading... regards, tom lane