SPI_CURSOR_FIND(3)

💅 SPI_CURSOR_FIND(3) 💅

okay so bestie, welcome to the PostgreSQL 15.19 docs — specifically the SPI_CURSOR_FIND(3) page, and honestly? it's a short one but it eats. let me walk you through it 🫶

---

✨ NAME ✨

SPI_cursor_find — find an existing cursor by name 🔍

---

✨ SYNOPSIS ✨

Portal SPI_cursor_find(const char * name)

---

✨ DESCRIPTION ✨

so SPI_cursor_find finds an existing portal by name. that's the whole vibe. 🎀

it's primarily useful for one specific thing: resolving a cursor name that some other function handed you back as text. like, someone gave you a name string and you're standing there like "ok but which portal is this 💀" — that's the moment this function exists for. iconic behavior honestly, main character energy.

---

✨ ARGUMENTS ✨

• const char * name — the name of the portal. that's it, that's the whole argument. very low maintenance, we love a simple signature 🌸

---

✨ RETURN VALUE ✨

a pointer to the portal with the specified name — or NULL if none was found. no portal, no pointer, no drama 🙈

---

✨ NOTES ✨

okay listen, this is the part where we get a little serious because it matters:

beware — this function can return a Portal object that does not have cursor-like properties. for example, it might not return tuples. 😭

so if you're just passing that Portal pointer along to other SPI functions? you're fine, bestie — they can defend themselves against these cases. but if you're going to be directly inspecting the Portal yourself? caution is appropriate. that's the whole warning, fr fr. read it, internalize it, don't rawdog a Portal inspection 💀👑

---

⭐ and that's the page! lowkey one of the shorter ones, but every detail is doing its job. this was pulled from the PostgreSQL 15.19 Documentation set, dated 2026 — same version, same date, same SPI_CURSOR_FIND(3) energy, just with way more sparkle ✨💅🎀

go find those portals, bestie — you got this 💖🌈