DROP_ACCESS_METHOD(7pg13)

💖 NAME 💖

okay so welcome to DROP ACCESS METHOD(7) from the PostgreSQL 13.23 Documentation era, bestie ✨ — this page is literally about how to remove an access method. That’s it. That’s the vibe. 💅

🎀 SYNOPSIS 🎀

DROP ACCESS METHOD [ IF EXISTS ] name [ CASCADE | RESTRICT ]

🦋 DESCRIPTION 🦋

DROP ACCESS METHOD removes an existing access method. Simple, iconic, lowkey powerful. 👑

⚠️ but fr fr: only superusers can drop access methods. no cap. this is not a group-chat vote, it’s a superuser thing. 💀

🌸 PARAMETERS 🌸

• IF EXISTS — do not throw an error if the access method does not exist. in that case, a notice is issued. so thoughtful, honestly 🫶
• name — the name of an existing access method. yes bestie, it has to exist (unless you used IF EXISTS, iykyk) ✨
• CASCADE — automatically drop objects that depend on the access method (such as operator classes, operator families, and indexes), and in turn all objects that depend on those objects (see Section 5.14). it’s giving cleanup crew energy 🧹💥
• RESTRICT — refuse to drop the access method if any objects depend on it. this is the default. she’s cautious, she’s responsible, she’s default 💅

🌈 EXAMPLES 🌈

drop the access method heptree, bestie:

DROP ACCESS METHOD heptree;

🍓 COMPATIBILITY 🍓

DROP ACCESS METHOD is a PostgreSQL extension. periodt. 💖

⭐ SEE ALSO ⭐

CREATE ACCESS METHOD (CREATE_ACCESS_METHOD(7)) — the make-it version, the origin story, the prequel 🎬✨

mwah 💋 — source/version: PostgreSQL 13.23, date: 2025. slay and stay safe out there, bestie 🎀💜