SPI_EXECP(3)

💖 NAME 💖

okay so bestie, this is SPI_EXECP(3) — the PostgreSQL 13.23 manual page for SPI_execp, and it literally executes a statement in read/write mode. slay. ✨

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

SPI_execp is the same as SPI_execute_plan, except the latter's read_only parameter is always taken as false. no cap, it's giving read/write energy. 🔥

🎀 ARGUMENTS 🎀

• SPIPlanPtr plan — the prepared statement, returned by SPI_prepare. main character argument fr fr. 👑
• Datum * values — an array of actual parameter values. It must have the same length as the statement's number of arguments. match the energy, bestie. 💅
• const char * nulls — an array describing which parameters are null. It must have the 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. lowkey important, don't skip this. 🌸

• long count — maximum number of rows to return, or 0 for no limit. iconic little limit knob. ⭐

🌈 RETURN VALUE 🌈

See SPI_execute_plan. 👑

SPI_processed and SPI_tuptable are set as in SPI_execute if successful. periodt. 💜

🌷 that's the whole page, bestie — straight from the PostgreSQL 13.23 docs, dated 2025. SPI_EXECP(3) out. 💅✨