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: Thu, 20 Apr 2000 11:06:33 -0400
Message-ID: <2182.956243193@sss.pgh.pa.us> (raw)
In-Reply-To: <38FEB8DB.DBC3460E@mcmail.com>
References: <38FB6FA1.C63B030B@mcmail.com>
<16483.956019092@sss.pgh.pa.us>
<38FEB8DB.DBC3460E@mcmail.com>
Tim Brookes <tim.brookes@mcmail.com> writes:
> 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?
Current CVS sources --- ie, 7.0RC1 plus or minus a little bit. But as
far as I can tell from the CVS logs, not much has been done to libpq++
since 6.5; there's certainly nothing in the logs about fixing memory
leaks. So I'd have expected 6.5 to behave the same. Interesting.
> callproc(){
> PgDatabase* loStatsdb;
> loStatsdb = new PgDatabase("");
> delete loStatsdb;
> };
> main(){
> while(1){
> callproc();
> };
> };
AFAIR, my test program looked just like that except it specified a
database name --- new PgDatabase("dbname=regression") or some such.
I wonder if it could be platform- or configuration-specific. What
options did you give to configure?
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: <2182.956243193@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