SPI_FREETUPTABLE(3)

🎀 SPI_FREETUPTABLE(3) 🎀

okay bestie, welcome to the PostgreSQL 18.6 docs, section 3, and today's main character is SPI_freetuptable — the girl whose whole job is freeing a row set created by SPI_execute or a similar function. she's not glamorous, she's just necessary. 💅

✨ NAME ✨

SPI_freetuptable — free a row set created by SPI_execute or a similar function

🦋 SYNOPSIS 🦋

void SPI_freetuptable(SPITupleTable * tuptable)

💖 DESCRIPTION 💖

so SPI_freetuptable literally frees a row set that some prior SPI command execution function made — think SPI_execute and its friends. that's why you'll usually see her getting called with the global variable SPI_tuptable as her argument. it's giving "just take out the trash you already made" 🗑️✨

she's highkey useful when your SPI-using C function needs to run multiple commands and does not want to be dragging the results of earlier commands around until the whole thing ends. like, let it go, girl. 💅

but fr fr, note this: any row sets you never freed will get freed anyway at SPI_finish. no cap. also — if a subtransaction gets started and then aborted within the execution of an SPI-using C function, SPI automatically frees any row sets that were created while that subtransaction was running. so the cleanup crew shows up either way. 🧚

and here's the glow-up: beginning in PostgreSQL 9.3, SPI_freetuptable contains guard logic to protect against duplicate deletion requests for the same row set. in previous releases? duplicate deletions would lead to crashes. 💀 yeah. not iconic. we do not miss her.

🌸 ARGUMENTS 🌸

• SPITupleTable * tuptable — pointer to the row set to free, or NULL to do nothing (yes, NULL is the "lol never mind, no thoughts, head empty" option and she respects it 🙈)

and that's the whole page, bestie — short, sweet, and fully slaying. this was PostgreSQL 18.6, dated 2026, brought to you by the fine folks who write the docs so we don't have to guess. 🫶 stay freed, stay safe, and always free your row sets before your function dips. 💖✨