DROP_ACCESS_METHOD(7pg17)

💅 DROP_ACCESS_METHOD(7pg17) 💅

Okay bestie, this is the manual page for DROP_ACCESS_METHOD(7pg17) from the PostgreSQL 17.11 Documentation — and we're gonna make removing access methods make sense. No cap. 🫶

🌸 NAME 🌸

DROP_ACCESS_METHOD — remove an access method. That's the whole vibe: access method, but make it gone. ✨

🎀 SYNOPSIS 🎀

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

🦋 DESCRIPTION 🦋

So DROP ACCESS METHOD literally removes an existing access method. Only superusers can drop access methods — superuser privilege check, periodt. 👑

✨ PARAMETERS ✨

• IF EXISTS — do not throw an error if the access method does not exist. In that case a notice is issued. Lowkey merciful. 🙈
• name — the name of an existing access method. Your target. 💅
• 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.15). It's giving chain reaction. 🔥
• RESTRICT — refuse to drop the access method if any objects depend on it. This is the default. Safety first, bestie. 🛡️

🍓 EXAMPLES 🍓

Drop the access method heptree:

DROP ACCESS METHOD heptree;

🌈 COMPATIBILITY 🌈

DROP ACCESS METHOD is a PostgreSQL extension. It's PostgreSQL's own little moment, iykyk. 💜

👑 SEE ALSO 👑

• CREATE ACCESS METHOD (CREATE_ACCESS_METHOD(7)) — the create-side counterpart, fr fr.

---

💖 Sign-off tea: this page comes from PostgreSQL 17.11 Documentation, dated 2026, and it's the DROP ACCESS METHOD(7) manual page. Byeee, go drop your access methods responsibly! 💋✨