SPI_REGI...GGER_DATA(3)

✨ SPI_REGI...GGER_DATA(3) ✨

okay so bestie, we're in the PostgreSQL 14.24 Documentation today and this page is literally about letting your trigger's lil' ephemeral relations slide into your SPI queries 🫶 it's giving backstage pass energy, iykyk 💅

---

🌸 NAME 🌸

SPI_register_trigger_data — make ephemeral trigger data available in SPI queries ✨

---

🦋 SYNOPSIS 🦋

int SPI_register_trigger_data(TriggerData *tdata)

---

💖 DESCRIPTION 💖

okay so SPI_register_trigger_data makes any ephemeral relations captured by a trigger available to queries planned and executed through the current SPI connection 🌈

for now, "ephemeral relations" means the transition tables captured by an AFTER trigger that was defined with a REFERENCING OLD/NEW TABLE AS ... clause 💫 that's the whole vibe.

the way this works: a PL trigger handler function should call this function after connecting 🎀 like, connect first, register second, no cap.

---

🎀 ARGUMENTS 🎀

• TriggerData *tdata — the TriggerData object that got passed to a trigger handler function as fcinfo->context 🧚 it's the lil' bundle of trigger context, hand it over as-is.

---

🍓 RETURN VALUE 🍓

if the execution of the command was successful then the following (nonnegative) value will be returned, slay:

• SPI_OK_TD_REGISTER — if the captured trigger data (if any) has been successfully registered 👑 note the "(if any)" bestie, sometimes there's just nothing to register and that's fine.

on error, one of the following negative values is returned 😭:

• SPI_ERROR_ARGUMENT — if tdata is NULL 💀 like, you can't just pass nothing, that's not the move.
• SPI_ERROR_UNCONNECTED — if called from an unconnected C function 🙈 connect first, ask questions later.
• SPI_ERROR_REL_DUPLICATE — if the name of any trigger data transient relation is already registered for this connection 🔥 that name is taken, bestie, pick another one.

fr fr check the return value, don't just vibe past it — a negative number means something went sideways 💜

---

⭐ SEE ALSO ⭐

hmm, the original doesn't list any SEE ALSO references here, so nothing to link — go look at the rest of the SPI docs if you're nosy 🦋

---

and that's the whole page, periodt 💅 this was brought to you by PostgreSQL 14.24, dated 2026 — same SPI_REGI...GGER_DATA(3) energy, mwah 🎀✨