SPI_FREETUPTABLE(3)

🌸 NAME 🌸

okay so bestie, this is SPI_FREETUPTABLE(3) from the PostgreSQL 13.23 Documentation — it frees a row set created by SPI_execute or a similar function. periodt. 💅

✨ SYNOPSIS ✨

void SPI_freetuptable(SPITupleTable * tuptable)

🦋 DESCRIPTION 🦋

SPI_freetuptable frees a row set made by a prior SPI command execution function, like SPI_execute. Because of that, it’s often called with the global variable SPI_tuptable as its argument. iconic behavior, honestly. 💖

This function is useful if an SPI-using C function needs to execute multiple commands and does not want to keep the results of earlier commands around until it ends. Note that any unfreed row sets will be freed anyway at SPI_finish. Also, if a subtransaction is started and then aborted within execution of an SPI-using C function, SPI automatically frees any row sets created while the subtransaction was running. the cleanup crew stays booked and busy 🧹✨

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. crashes, bestie — not the vibe. 💀

🎀 ARGUMENTS 🎀

• SPITupleTable * tuptable — pointer to the row set to free, or NULL to do nothing. simple, clean, no drama 🫶

mwah 💖 — PostgreSQL 13.23 Documentation, dated 2025. Now go free those row sets, bestie! 🌈⭐