---
title: "SPI_execp"
id: spi-spi-execp
pg_version: "20devel"
---

<a id="spi-spi-execp"></a>

# SPI_execp — execute a statement in read/write mode

## Synopsis

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

<a id="id-1.8.12.8.18.5"></a>

## Description

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

<a id="id-1.8.12.8.18.6"></a>

## 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 <a id="id-1.8.12.8.18.7"></a>

## Return Value

See `SPI_execute_plan`. 

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