SPI_CURSOR_FIND(3)

🎀 SPI_CURSOR_FIND(3) 🎀

okay so bestie, we are lowkey deep in the PostgreSQL 13.23 Documentation, and this page is literally called SPI_CURSOR_FIND. It’s giving “find a portal by name” main character energy, and we’re gonna walk through it together, no cap. 💅

🌸 NAME 🌸

SPI_cursor_find — find an existing cursor by name. That’s the whole vibe. ✨

🦋 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. So basically: portal by name, found. The main-character use case? Resolving a cursor name that some other function handed you back as text. Iconic. 🫶

🌈 ARGUMENTS 🌈

• const char * name — the name of the portal. That’s it, that’s the argument. 🎀

⭐ RETURN VALUE ⭐

A pointer to the portal with the specified name, or NULL if none was found. Yep, that simple — if it’s not there, you get NULL, bestie. 🦋

⚠️ NOTES ⚠️

Beware, bestie: 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, for real, keep your eyes open when you’re digging into that Portal yourself. 🔥

xoxo, stay hydrated and portal-safe — signed off by the PostgreSQL 13.23 docs, dated 2025 💜💅