]> granicus.if.org Git - postgresql/commit
Change SPI functions to use a `long' when specifying the number of tuples
authorNeil Conway <neilc@samurai.com>
Mon, 2 May 2005 00:37:07 +0000 (00:37 +0000)
committerNeil Conway <neilc@samurai.com>
Mon, 2 May 2005 00:37:07 +0000 (00:37 +0000)
commitf478856c7f875efceea27f30041965571815f05b
treef57db3d9edb2a059089da30aa06b4abb75a7d166
parent6c412f0605afeb809014553ff7ad28cf9ed5526b
Change SPI functions to use a `long' when specifying the number of tuples
to produce when running the executor. This is consistent with the internal
executor APIs (such as ExecutorRun), which also use a long for this purpose.
It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as
LONG_MAX, this wouldn't have worked on platforms where int and long are of
different sizes. Per report from Tzahi Fadida.
doc/src/sgml/spi.sgml
src/backend/executor/spi.c
src/include/executor/spi.h
src/pl/plpgsql/src/pl_exec.c
src/pl/plpython/plpython.c