SPI memory overrun details

Started by Katsaros Kwn/nosover 21 years ago2 messagesgeneral
Jump to latest
#1Katsaros Kwn/nos
ntinos@aueb.gr

Hi,

I read in the documentation of SPI functions that an SPI_cursor is used
to avoid memory overrun in cases where a query returns many rows. I'd
like to learn more about this. Is their any place that I could find more
detailed information (e.g. max size of results, threshold - available
memory etc.)?

I searched the archives but nothing.

Regards,
Ntinos Katsaros

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Katsaros Kwn/nos (#1)
Re: SPI memory overrun details

"Katsaros Kwn/nos" <ntinos@aueb.gr> writes:

I read in the documentation of SPI functions that an SPI_cursor is used
to avoid memory overrun in cases where a query returns many rows. I'd
like to learn more about this. Is their any place that I could find more
detailed information (e.g. max size of results, threshold - available
memory etc.)?

You could look at plpgsql's use of SPI cursors for an example.

regards, tom lane