SPI_CONNECT(3)

🌸 SPI_CONNECT(3) — connect a C function to the SPI manager 💅

manual page: SPI_CONNECT(3) — yes bestie, the manual name is folded in right here ✨

💖 NAME 💖

SPI_connect, SPI_connect_ext — connect a C function to the SPI manager, periodt.

✨ SYNOPSIS ✨

int SPI_connect(void)

int SPI_connect_ext(int options)

🦋 DESCRIPTION 🦋

okay so SPI_connect opens a connection from a C function invocation to the SPI manager. You must call this function if you want to execute commands through SPI. Some utility SPI functions can be called from unconnected C functions — iykyk. No cap, that’s the whole vibe.

SPI_connect_ext does the same but has an argument that allows passing option flags. Currently, the following option values are available:

• SPI_OPT_NONATOMIC — sets the SPI connection to be nonatomic, which means that transaction control calls (SPI_commit, SPI_rollback) are allowed. Otherwise, calling those functions will result in an immediate error. fr fr, that immediate error is not a vibe.

SPI_connect() is equivalent to SPI_connect_ext(0). literally the same energy 🫶

🌈 RETURN VALUE 🌈

• SPI_OK_CONNECT — on success 🎉
• SPI_ERROR_CONNECT — on error 😭

vibe check passed = success, vibe check failed = error, iykyk

xoxo, from the PostgreSQL 17.11 documentation, dated 2026 — page SPI_CONNECT(3) 💖