a bug that might be related to BUG #1739

From: Tzahi Fadida <tzahi_ml(at)myrealbox(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: a bug that might be related to BUG #1739
Date: 2005-07-03 23:10:15
Message-ID: 009a01c58024$653642c0$0b00a8c0@llord
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I am writing C functions and I use SPI extensively.
Till now I used cursors and there was no memory leaks.
But now I do thousands of inserts using SPI_execp
and I also give it parameters.
Now, when I execute the insert about 50-100 times I loose
around 100kb memory and SPI_finish() does not release this
memory (although I really can't do SPI finish in normal executions
all the time since I have open cursors).
I tried spipush connect query finish pop. but the leak stays.
I really need this resolved since I can reach a million runs
in my functions and thus my whole memory can be depleted.

I use 8.0.3

Another clue. The relation I am adding to have a unique index.
If I do about 100 inserts and the relation have the index I loose around
100kb.
without the index on the relation I loose around 40kb.

Btw, execp with selects also looses memory. Only cursors seems immune to
this.
Please help,
10x.

Regards,
tzahi.

WARNING TO SPAMMERS: see at
http://members.lycos.co.uk/my2nis/spamwarning.html

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tzahi Fadida 2005-07-04 02:18:33 Re: a bug that might be related to BUG #1739
Previous Message Tom Lane 2005-07-03 22:53:41 Re: a bug that might be related to BUG #1739