Temp Table Memory Leak

From: Kristofer Munn <kmunn(at)munn(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Temp Table Memory Leak
Date: 2000-01-17 04:40:44
Message-ID: Pine.LNX.4.04.10001160208180.27063-200000@munn.com
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).

Thanks...

- K

Kristofer Munn * KMI * 973-509-9414 * AIM KrMunn * http://www.munn.com/

Attachment Content-Type Size
memleak.sql text/plain 5.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-17 05:01:27 Re: [HACKERS] Temp Table Memory Leak
Previous Message Hiroshi Inoue 2000-01-17 04:20:37 RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c)