DROP_OWNED(7pg18)

💅 DROP OWNED — ok bestie let's clean house

so this is the DROP OWNED page from the PostgreSQL 18.6 Documentation, manual section 7, and it's literally about removing database objects owned by a database role. no cap. 🎀

---

✨ NAME ✨

DROP OWNED — remove database objects owned by a database role 🧹💖

---

🌸 SYNOPSIS 🌸

DROP OWNED BY { name | CURRENT_ROLE | CURRENT_USER | SESSION_USER } [, ...] [ CASCADE | RESTRICT ]

---

🦋 DESCRIPTION 🦋

okay so here's the tea 🍓 — DROP OWNED drops all the objects within the current database that are owned by one of the specified roles. all of them. every last one. she's thorough like that. 💅

and it doesn't stop there, bestie. any privileges granted to the given roles on objects in the current database — or on shared objects (databases, tablespaces, configuration parameters) — will also be revoked. privileges? gone. objects? gone. it's giving spring cleaning but make it SQL. ✨

---

🎀 PARAMETERS 🎀

• name — the name of a role whose objects will be dropped, and whose privileges will be revoked. that's your target, bestie. 🎯
• CASCADE — automatically drop objects that depend on the affected objects, and in turn all objects that depend on those objects (see Section 5.15). it's a chain reaction, lowkey. 🌀
• RESTRICT — refuse to drop the objects owned by a role if any other database objects depend on one of the affected objects. this one is the default, so if you don't say anything, this is the energy you get. she's cautious. she's sensible. 🫶

---

👑 NOTES 👑

okay so the classic move — DROP OWNED is often used to prepare for the removal of one or more roles. you gotta clear the decks before you yeet the role. 🧚

but here's the catch, and it's important fr fr: because DROP OWNED only affects the objects in the current database, it's usually necessary to execute this command in each database that contains objects owned by a role that is to be removed. every. single. one. she's per-database, she said what she said. 😭

⚠️ using the CASCADE option might make the command recurse to objects owned by other users. not just your role. other users. just so you know. 💀

the REASSIGN OWNED command is an alternative that reassigns the ownership of all the database objects owned by one or more roles. however — and this is the plot twist — REASSIGN OWNED does not deal with privileges for other objects. 🙈

databases and tablespaces owned by the role(s) will not be removed. nope. those stay. 🌈

see Section 21.4 for more discussion. iykyk. ⭐

---

💜 COMPATIBILITY 💜

the DROP OWNED command is a PostgreSQL extension. she's homegrown. she's ours. periodt. 👑

---

🔥 SEE ALSO 🔥

• REASSIGN OWNED (REASSIGN_OWNED(7))
• DROP ROLE (DROP_ROLE(7))

---

and that's the whole page bestie!! 🫶 this was PostgreSQL 18.6, dated 2026, and honestly? iconic. go forth and drop responsibly. 💖✨🎀🦋🌸