From: Tim Brookes <tim.brookes@mcmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq++ memory problems
Date: Thu, 20 Apr 2000 08:59:24 +0100
Message-ID: <38FEB8DB.DBC3460E@mcmail.com> (raw)
References: <38FB6FA1.C63B030B@mcmail.com>
<16483.956019092@sss.pgh.pa.us>
OK
So I have downloaded and set up version 6.5.3 on a test system. I then
altered the code on the example so that it no longer uses the PgEnv class.
I set my environment variable and ran the program now as below. I still get
a huge memory leak.
Can I ask you what version you are using?
callproc(){
PgDatabase* loStatsdb;
loStatsdb = new PgDatabase("");
delete loStatsdb;
};
main(){
while(1){
callproc();
};
};
Rgds
Tim Brookes
Tom Lane wrote:
> 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: tim.brookes@mcmail.com, tgl@sss.pgh.pa.us
Subject: Re: libpq++ memory problems
In-Reply-To: <38FEB8DB.DBC3460E@mcmail.com>
* 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