From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ian Harding" <ianh(at)tpchd(dot)org> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Memory Errors... |
Date: | 2002-09-19 16:18:56 |
Message-ID: | 26631.1032452336@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Ian Harding" <ianh(at)tpchd(dot)org> writes:
> It is pltcl [not plpgsql]
Ah. I don't think we've done much of any work on plugging leaks in
pltcl :-(.
> It hurts when I do this:
> drop function memleak();
> create function memleak() returns int as '
> for {set counter 1} {$counter < 100000} {incr counter} {
> set sql "select ''foo''"
> spi_exec "$sql"
> }
> ' language 'pltcl';
> select memleak();
Yeah, I see very quick memory exhaustion also :-(. Looks like the
spi_exec call is the culprit, but I'm not sure exactly why ...
anyone have time to look at this?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-19 16:22:25 | Re: Proposal for resolving casting issues |
Previous Message | Tom Lane | 2002-09-19 16:07:54 | Re: killing process question |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-19 16:51:12 | Re: to_char() code cleanup |
Previous Message | Karel Zak | 2002-09-19 09:14:58 | to_char(FM9.9) bug fix |