From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Brookes <tim.brookes@mcmail.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq++ memory problems
Date: Mon, 17 Apr 2000 20:51:32 -0400
Message-ID: <16483.956019092@sss.pgh.pa.us> (raw)
In-Reply-To: <38FB6FA1.C63B030B@mcmail.com>
References: <38FB6FA1.C63B030B@mcmail.com>
Tim Brookes <tim.brookes@mcmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, tim.brookes@mcmail.com
Subject: Re: libpq++ memory problems
In-Reply-To: <16483.956019092@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox