2005/6/28, Jean-Max Reymond <[EMAIL PROTECTED]>:
> For my application (in real life) afer millions of spi_exec_query, it
> grows up to 1Gb :-(
OK, now in 2 lines:
CREATE FUNCTION jmax() RETURNS integer
AS $_$use strict;
for (my $i=0; $i<1000;$i++) {
spi_exec_query("select 'foo'")
2005/6/28, Tom Lane <[EMAIL PROTECTED]>:
> Jean-Max Reymond <[EMAIL PROTECTED]> writes:
> > I have a stored procedure written in perl and I doubt that perl's
> > garbage collector is working :-(
> > after a lot of work, postmaster has a size of 1100 Mb and I think
> > that the keyword "undef" has
Jean-Max Reymond <[EMAIL PROTECTED]> writes:
> I have a stored procedure written in perl and I doubt that perl's
> garbage collector is working :-(
> after a lot of work, postmaster has a size of 1100 Mb and I think
> that the keyword "undef" has no effects.
Check the PG list archives --- there's
On Jun 27, 2005, at 4:46 PM, Jean-Max Reymond wrote:
Hi,
I have a stored procedure written in perl and I doubt that perl's
garbage collector is working :-(
after a lot of work, postmaster has a size of 1100 Mb and I think
that the keyword "undef" has no effects.
Before tuning my procedure, doe
Hi,
I have a stored procedure written in perl and I doubt that perl's
garbage collector is working :-(
after a lot of work, postmaster has a size of 1100 Mb and I think
that the keyword "undef" has no effects.
Before tuning my procedure, does it exist a known issue, a workaround ?
--
Jean-Max R
