Memory leak

From: Michael <grim(at)argh(dot)demon(dot)co(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Memory leak
Date: 1999-08-25 06:57:13
Message-ID: 37C393C9.8EE5EBD0@argh.demon.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all

I have just isolated a big problem in one of my applications and it turns out
to be a memory leak in postgresql on a VERY basic piece of functionality

It just caused a backend to grow to 133 MB in 4 hours running, which is
obviously not good

Simple piece of C code to demonstrate this:

for (loopa=0;loopa < 100000;loopa++)
{
result=PQexec(dbase,"create table test_table ( "
"value int,wordnum int,refnum int,word text)");
PQclear(result);

result=PQexec(dbase,"drop table test_table");
PQclear(result);
}

And watch the memory risssssssse

On an aside, any idea how long till there is a fix for the vacuum analyze
crash, as it is cripling me having that happen.

Final question... Is there a really really good reason that when a backend
crashes, all the other backends die and close connection rather than simply
re-initialising their connections. If it just reinitialised transparently that
would make it a LOT easier than having to have an extra test to see if the
backend has mysteriously crashed after EVERY query!

Thanx

M Simms

--
#define z(x,y) for (x=0;x<y;x++){
main(){long int i[3]={1214606444,1864390511,1919706122};int x,y;
z(x,3)z(y,4)putchar((i[x]>>((3-y)<<3))&(255));
}}}

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jens Felber 1999-08-25 09:26:54 changing between 6.4.1 and 6.5
Previous Message Hub.Org News Admin 1999-08-25 05:05:38