SPI_CURSOR_FIND(3)

🎀 the SPI_cursor_find bestie briefing 🎀

okay so welcome to SPI_CURSOR_FIND(3), straight from the PostgreSQL 17.11 Documentation 💖 this one is lowkey short but highkey useful, so let’s get into it ✨

🌸 NAME 🌸

SPI_cursor_find - find an existing cursor by name 🎀

🦋 SYNOPSIS 🦋

Portal SPI_cursor_find(const char * name)

✨ DESCRIPTION ✨

SPI_cursor_find finds an existing portal by name. This is primarily useful to resolve a cursor name returned as text by some other function. no cap, that’s the whole glow-up 💅

🎀 ARGUMENTS 🎀

• const char * name — name of the portal 🫶

🔥 RETURN VALUE 🔥

pointer to the portal with the specified name, or NULL if none was found 💖

💀 NOTES 💀

Beware that this function can return a Portal object that does not have cursor-like properties; for example it might not return tuples. If you simply pass the Portal pointer to other SPI functions, they can defend themselves against such cases, but caution is appropriate when directly inspecting the Portal. like bestie, peek responsibly 👀✨

that’s the whole page, bestie 🫶 — brought to you by PostgreSQL 17.11, dated 2026. mwah 💋✨