Movatterモバイル変換


[0]ホーム

URL:


November 13, 2025: PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 Released!
DocumentationPostgreSQL devel (2025-12-17 20:34:52 - git commitab8af1db430)
Supported Versions:Current (18) /17 /16 /15 /14
Development Versions:devel
Unsupported versions:13 /12 /11 /10 /9.6 /9.5 /9.4 /9.3 /9.2 /9.1 /9.0 /8.4 /8.3 /8.2 /8.1 /8.0 /7.4
This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for thecurrent version, or one of the other supported versions listed above instead.
SPI_execp
Prev Up45.1. Interface FunctionsHome Next

SPI_execp

SPI_execp — execute a statement in read/write mode

Synopsis

int SPI_execp(SPIPlanPtrplan, Datum *values, const char *nulls, longcount)

Description

SPI_execp is the same asSPI_execute_plan, with the latter'sread_only parameter always taken asfalse.

Arguments

SPIPlanPtrplan

prepared statement (returned bySPI_prepare)

Datum *values

An array of actual parameter values. Must have same length as the statement's number of arguments.

const char *nulls

An array describing which parameters are null. Must have same length as the statement's number of arguments.

Ifnulls isNULL thenSPI_execp assumes that no parameters are null. Otherwise, each entry of thenulls array should be' ' if the corresponding parameter value is non-null, or'n' if the corresponding parameter value is null. (In the latter case, the actual value in the correspondingvalues entry doesn't matter.) Note thatnulls is not a text string, just an array: it does not need a'\0' terminator.

longcount

maximum number of rows to return, or0 for no limit

Return Value

SeeSPI_execute_plan.

SPI_processed andSPI_tuptable are set as inSPI_execute if successful.


Prev Up Next
SPI_execute_plan_with_paramlist Home SPI_cursor_open

[8]ページ先頭

©2009-2025 Movatter.jp