Re: [HACKERS] Temp Table Memory Leak

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Kristofer Munn <kmunn(at)munn(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Temp Table Memory Leak
Date: 2000-01-17 05:04:39
Message-ID: 200001170504.AAA11977@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hi again...
>
> I've discovered (or perhaps re-discovered) what seems to be a memory leak
> involving temp tables. It's so bad that I make a script (which runs as a
> daemon) close the backend connection and reconnect each time it runs the
> offending command sequences. Without the reset I've seen the backend grow
> to over 100 megs in size in a matter of a couple of minutes.
>
> I've created a sample case that reproduces the error that I will attach
> with this message. Basically, I create a 50 column temp table (with no
> rows in it) and then run updates on each column in succession. The
> backend gets large pretty quick - I'm seeing about 12Megs after running
> the enclosed script which does an update on all 50 columns 3 times (150
> updates).

Is this with 6.5.* or 7.0. If it is 6.5.*, can you try it with our
current tree for testing purposes. I think you will find it is fixed.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kristofer Munn 2000-01-17 05:06:42 Re: [HACKERS] Temp Table Memory Leak
Previous Message Tom Lane 2000-01-17 05:01:27 Re: [HACKERS] Temp Table Memory Leak