1SPI_EXECP(3)             PostgreSQL 13.4 Documentation            SPI_EXECP(3)
2
3
4

NAME

6       SPI_execp - execute a statement in read/write mode
7

SYNOPSIS

9       int SPI_execp(SPIPlanPtr plan, Datum * values, const char * nulls, long count)
10

DESCRIPTION

12       SPI_execp is the same as SPI_execute_plan, with the latter's read_only
13       parameter always taken as false.
14

ARGUMENTS

16       SPIPlanPtr plan
17           prepared statement (returned by SPI_prepare)
18
19       Datum * values
20           An array of actual parameter values. Must have same length as the
21           statement's number of arguments.
22
23       const char * nulls
24           An array describing which parameters are null. Must have same
25           length as the statement's number of arguments.
26
27           If nulls is NULL then SPI_execp assumes that no parameters are
28           null. Otherwise, each entry of the nulls array should be ' ' if the
29           corresponding parameter value is non-null, or 'n' if the
30           corresponding parameter value is null. (In the latter case, the
31           actual value in the corresponding values entry doesn't matter.)
32           Note that nulls is not a text string, just an array: it does not
33           need a '\0' terminator.
34
35       long count
36           maximum number of rows to return, or 0 for no limit
37

RETURN VALUE

39       See SPI_execute_plan.
40
41       SPI_processed and SPI_tuptable are set as in SPI_execute if successful.
42
43
44
45PostgreSQL 13.4                      2021                         SPI_EXECP(3)
Impressum