Re: nested SQL with SPI

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Wagner <wagner(at)imsd(dot)uni-mainz(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: nested SQL with SPI
Date: 2001-09-04 14:01:45
Message-ID: 26123.999612105@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Markus Wagner <wagner(at)imsd(dot)uni-mainz(dot)de> writes:
> this would mean that all result tables are kept in memory until the trigger
> function exits?

Until you do SPI_freetuptable or SPI_finish, yes, an SPI result sticks
around.

> What do you mean with "copy it and associated globals into locals", just the
> pointers or the data itself?

Just the pointer. You may or may not need to hang onto SPI_processed,
SPI_lastoid, or SPI_result; a copy of SPI_tuptable might be enough for
your purposes.

If the docs don't seem clear enough to you, feel free to submit a doc
patch ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2001-09-04 14:10:48 Re: Is it possible to default all number data to numeric type?
Previous Message Oliver Elphick 2001-09-04 12:33:58 Re: Problem with numeric and operators