SPI_REGISTER_RELATION(3pg17)

✨ NAME ✨

Okay bestie, welcome to SPI_REGISTER_RELATION(3) from the PostgreSQL 17.11 Documentation 💖 — this page is literally about SPI_register_relation: make an ephemeral named relation available by name in SPI queries. Slay.

🌸 SYNOPSIS 🌸

int SPI_register_relation(EphemeralNamedRelation enr)

🦋 DESCRIPTION 🦋

So SPI_register_relation makes an ephemeral named relation — with all its associated information — available to queries that are planned and executed through the current SPI connection. It’s giving “registry entry, but make it query-visible” ✨.

🎀 ARGUMENTS 🎀

• EphemeralNamedRelation enr — the ephemeral named relation registry entry. That’s the whole argument, bestie 🫶.

💅 RETURN VALUE 💅

If the execution of the command was successful, then this nonnegative value gets returned:

• SPI_OK_REL_REGISTER — if the relation has been successfully registered by name 👑.

On error, one of these negative values is returned:

• SPI_ERROR_ARGUMENT — if enr is NULL or its name field is NULL 😭.
• SPI_ERROR_UNCONNECTED — if called from an unconnected C function 💀.
• SPI_ERROR_REL_DUPLICATE — if the name specified in the name field of enr is already registered for this connection 🙈.

Negative return values mean error vibes, periodt. Nonnegative means success — no cap.

mwah 💋 — from the PostgreSQL 17.11 docs, dated 2026, page SPI_REGISTER_RELATION(3). Bye bestie! 🎀🦋💜