Re: a bug that might be related to BUG #1739

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tzahi Fadida <tzahi_ml(at)myrealbox(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: a bug that might be related to BUG #1739
Date: 2005-07-03 22:53:41
Message-ID: 20751.1120431221@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tzahi Fadida <tzahi_ml(at)myrealbox(dot)com> writes:
> 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.

If SPI_execp leaked memory then so would almost any plpgsql function,
so I'm inclined to think the leak is in your own code. Post a complete
example if you want it investigated.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tzahi Fadida 2005-07-03 23:10:15 a bug that might be related to BUG #1739
Previous Message Tom Lane 2005-07-03 21:57:41 Re: BUG #1739: memory leak in pl/perl with spi_exec_query