> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/server-programming/spi/spi-interface/spi-spi-execp.md).

# SPI\_execp

### SPI\_execp

SPI\_execp — execute a statement in read/write mode

### Synopsis

```

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

### Description

`SPI_execp` is the same as `SPI_execute_plan`, with the latter's *`read_only`* parameter always taken as `false`.

### Arguments

`SPIPlanPtr plan` : prepared statement (returned by `SPI_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.

```
If *`nulls`* is `NULL` then
`SPI_execp` assumes that no parameters
are null. Otherwise, each entry of the *`nulls`*
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
corresponding *`values`* entry doesn't matter.) Note
that *`nulls`* is not a text string, just an array:
it does not need a `'\0'` terminator.
```

`long count` : maximum number of rows to return, or `0` for no limit

### Return Value

See `SPI_execute_plan`.

`SPI_processed` and `SPI_tuptable` are set as in `SPI_execute` if successful.

***

原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/spi-spi-execp.html)（英文原文，待翻譯）


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.postgresql.tw/server-programming/spi/spi-interface/spi-spi-execp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.