SPI_UNRE..._RELATION(3)

💖 SPI_UNRE..._RELATION(3) 💖

hey bestie, welcome to the PostgreSQL 17.11 Documentation page for SPI_unregister_relation, aka the manual page tagged SPI_UNRE..._RELATION(3). it's giving “clean up your ephemeral relation registry” energy, and honestly? iconic. ✨

🌸 NAME 🌸

SPI_unregister_relation — remove an ephemeral named relation from the registry 🫶

🦋 SYNOPSIS 🦋

int SPI_unregister_relation(const char * name)

🎀 DESCRIPTION 🎀

okay so SPI_unregister_relation removes an ephemeral named relation from the registry for the current connection. that's the whole assignment, and it ate. 💅

🍓 ARGUMENTS 🍓

• const char * name — the relation registry entry name, bestie. that's the name it's looking for in the registry. 🎯

🔥 RETURN VALUE 🔥

if the execution of the command was successful, then you get the following nonnegative value:

• SPI_OK_REL_UNREGISTER — returned if the tuplestore has been successfully removed from the registry. slay, it worked! ✅

on error, one of these negative values is returned:

• SPI_ERROR_ARGUMENT — returned if name is NULL. oop, bestie, the name is missing. 😭
• SPI_ERROR_UNCONNECTED — returned if called from an unconnected C function. not connected, not the vibe. 🫠
• SPI_ERROR_REL_NOT_FOUND — returned if name is not found in the registry for the current connection. it searched, and it was not there. 💀

mwah 💋 — this little manual moment was brought to you by PostgreSQL 17.11, dated 2026, and the manual tag SPI_UNRE..._RELATION(3). periodt. 👑🌈