SPI_execute_extended — execute a command with out-of-line parameters
int SPI_execute_extended(const char *
command, const SPIExecuteOptions *
SPI_execute_extended executes a command that might include references to externally supplied parameters. The command text refers to a parameter as
$, and the
options->params object (if supplied) provides values and type information for each such symbol. Various execution options can be specified in the
options struct, too.
options->params object should normally mark each parameter with the
PARAM_FLAG_CONST flag, since a one-shot plan is always used for the query.
options->dest is not NULL, then result tuples are passed to that object as they are generated by the executor, instead of being accumulated in
SPI_tuptable. Using a caller-supplied
DestReceiver object is particularly helpful for queries that might generate many tuples, since the data can be processed on-the-fly instead of being accumulated in memory.
const char *
const SPIExecuteOptions *
struct containing optional arguments
Callers should always zero out the entire
options struct, then fill whichever fields they want to set. This ensures forward compatibility of code, since any fields that are added to the struct in future will be defined to behave backwards-compatibly if they are zero. The currently available
options fields are:
data structure containing query parameter types and values; NULL if none
true for read-only execution
true allows non-atomic execution of CALL and DO statements
maximum number of rows to return, or
0 for no limit
DestReceiver object that will receive any tuples emitted by the query; if NULL, result tuples are accumulated into a
SPI_tuptable structure, as in
This field is present for consistency with
SPI_execute_plan_extended, but it is ignored, since the plan used by
SPI_execute_extended is never saved.
The return value is the same as for
options->dest is NULL,
SPI_tuptable are set as in
options->dest is not NULL,
SPI_processed is set to zero and
SPI_tuptable is set to NULL. If a tuple count is required, the caller's
DestReceiver object must calculate it.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.