SPI_FREETUPLE(3)

okay so bestie, welcome to SPI_FREETUPLE(3) — that's the manual page name, bestie — straight from the PostgreSQL 16.15 Documentation. We're talking about SPI_freetuple, and it's giving short-and-sweet. Let's go 💅✨

💖 NAME 💖

SPI_freetuple — free a row allocated in the upper executor context 🫶

🦋 SYNOPSIS 🦋

void SPI_freetuple(HeapTuple row)

look at that signature: one function, one HeapTuple argument, zero chaos 🌸

🎀 DESCRIPTION 🎀

SPI_freetuple frees a row that was previously allocated in the upper executor context. That's the whole job, and it does it 💅

This function is no longer different from plain heap_freetuple. It's kept just for backward compatibility of existing code. So if you were thinking it had some secret extra sauce — nope, bestie, it's literally in its compatibility era now 😭. Existing code can keep using it, but it's not different from plain heap_freetuple anymore 🫶

🌈 ARGUMENTS 🌈

• HeapTuple row — the row to free. That's the one thing you hand over, and then it's freed 🎀

mwah 💋 this little page is from PostgreSQL 16.15, dated 2026 — bye bestie, go free that row 🌟