DROP_USER_MAPPING(7pg14)

💖 NAME 💖

DROP_USER_MAPPING — remove a user mapping for a foreign server. Yup bestie, you're on the DROP USER MAPPING(7pg14) page, and we're about to delete a mapping with main-character confidence ✨.

✨ SYNOPSIS ✨

DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_ROLE | CURRENT_USER | PUBLIC } SERVER server_name

🦋 DESCRIPTION 🦋

Okay so DROP USER MAPPING removes an existing user mapping from a foreign server. That's the whole vibe: mapping gone, periodt 💅.

The owner of a foreign server can drop user mappings for that server for any user. Also, a user can drop a user mapping for their own user name if USAGE privilege on the server has been granted to the user. Permission check: iconic, but real 🫶.

🎀 PARAMETERS 🎀

• IF EXISTS — do not throw an error if the user mapping does not exist. A notice is issued in this case. So it's lowkey the “no drama” flag 💖.
• user_name — user name of the mapping. CURRENT_ROLE, CURRENT_USER, and USER match the name of the current user. PUBLIC is used to match all present and future user names in the system. Present and future, bestie — that's a big mood 🌈.
• server_name — server name of the user mapping. Gotta name the server, obviously 🫶.

🌸 EXAMPLES 🌸

Drop a user mapping bob, server foo if it exists:

DROP USER MAPPING IF EXISTS FOR bob SERVER foo;

That's literally the example. Slay ✨.

🌈 COMPATIBILITY 🌈

DROP USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). The IF EXISTS clause is a PostgreSQL extension. So yes, standards girlie with a lil PostgreSQL extra 💖.

💜 SEE ALSO 💜

• CREATE USER MAPPING (CREATE_USER_MAPPING(7))
• ALTER USER MAPPING (ALTER_USER_MAPPING(7))

---

mwah 💖 signing off from the PostgreSQL 14.24 Documentation, dated 2026 — DROP USER MAPPING(7) out! 🎀✨