DROP_ACCESS_METHOD(7pg16)

💖 NAME 💖

DROP_ACCESS_METHOD — remove an access method. Yep bestie, this is the DROP ACCESS METHOD(7pg16) page, and we are literally learning how to drop an access method from your PostgreSQL world. No cap. ✨

✨ SYNOPSIS ✨

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

💅 DESCRIPTION 💅

DROP ACCESS METHOD removes an existing access method. Only superusers can drop access methods, so this is very much main character permission energy — if you’re not a superuser, this is not your moment. 👑

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the access method does not exist. A notice is issued in this case instead. So it’s like “bestie I checked, she’s not here” but official. 🙈
• name — the name of an existing access method. Literally the one you’re trying to drop. 💅
• 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). This is the “take everyone with you” option, so be careful. 😭
• RESTRICT — refuse to drop the access method if any objects depend on it. This is the default. Respectful, cautious, lowkey the responsible queen. 🫶

🌸 EXAMPLES 🌸

Drop the access method heptree:

DROP ACCESS METHOD heptree;

🦋 COMPATIBILITY 🦋

DROP ACCESS METHOD is a PostgreSQL extension. Periodt. 💅

🌈 SEE ALSO 🌈

• CREATE ACCESS METHOD (CREATE_ACCESS_METHOD(7)) — the create-side bestie, obviously. 💖

💖 okay that’s the whole page! Sourced from PostgreSQL 16.15, dated 2026 — DROP ACCESS METHOD(7) says bye bestie, go drop responsibly! 🎀✨