From: | Tim Brookes <tim(dot)brookes(at)mcmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: libpq++ memory problems |
Date: | 2000-04-20 07:59:24 |
Message-ID: | 38FEB8DB.DBC3460E@mcmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(dot)brookes(at)mcmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Zoltan Kovacs | 2000-04-20 12:02:52 | making winodbc driver better? |
Previous Message | Peter Mount | 2000-04-20 07:55:08 | RE: Is this usage correct ? |