CREATE_USER_MAPPING(7pg17)

💅 CREATE USER MAPPING 💅

okay bestie so this is CREATE USER MAPPING(7) from the PostgreSQL 17.11 Documentation, and it's literally about teaching your database how to log in as somebody else on a foreign server. very main character of it. let's go ✨

---

🎀 NAME 🎀

CREATE_USER_MAPPING — defines a new mapping of a user to a foreign server. that's it, that's the whole vibe 🫶

---

⭐ SYNOPSIS ⭐

CREATE USER MAPPING [ IF NOT EXISTS ] FOR { user_name | USER | CURRENT_ROLE | CURRENT_USER | PUBLIC }
    SERVER server_name
    [ OPTIONS ( option 'value' [ , ... ] ) ]

look at that syntax glow-up 😭 so many options to pick from, slay

---

🦋 DESCRIPTION 🦋

So CREATE USER MAPPING defines a mapping of a user to a foreign server. 🎀 A user mapping typically encapsulates connection information that a foreign-data wrapper uses together with the information encapsulated by a foreign server to access an external data resource. it's giving "here's everything you need to know to walk in the door" energy.

now, who's allowed to do this? the owner of a foreign server can create user mappings for that server for any user. also, a user can create a user mapping for their own user name if USAGE privilege on the server has been granted to the user. so you can absolutely be the one to do it for yourself — permission check, bestie 👑

---

💖 PARAMETERS 💖

• IF NOT EXISTS — do not throw an error if a mapping of the given user to the given foreign server already exists. a notice is issued in this case. ngl the important bit here: there is no guarantee that the existing user mapping is anything like the one that would have been created. so like... it won't yell at you, but it's not gonna match your fit either 🙈
• user_name — the name of an existing user that is mapped to foreign server. CURRENT_ROLE, CURRENT_USER, and USER all match the name of the current user. and when PUBLIC is specified, a so-called public mapping is created that is used when no user-specific mapping is applicable. it's the default outfit when nothing else fits 💜
• server_name — the name of an existing server for which the user mapping is to be created. yes, it has to already exist. no inventing servers out here 💀
• OPTIONS ( option 'value' [, ... ] ) — this clause specifies the options of the user mapping. the options typically define the actual user name and password of the mapping. option names must be unique. ✨ and the allowed option names and values are specific to the server's foreign-data wrapper — so like, ask them, not me 🌸

---

🌸 EXAMPLES 🌸

create a user mapping for user bob, server foo:

CREATE USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'secret');

ate, no crumbs. iconic 🔥

---

✨ COMPATIBILITY ✨

CREATE USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). standards queen 👑

---

🔮 SEE ALSO 🔮

• ALTER USER MAPPING (ALTER_USER_MAPPING(7))
• DROP USER MAPPING (DROP_USER_MAPPING(7))
• CREATE FOREIGN DATA WRAPPER (CREATE_FOREIGN_DATA_WRAPPER(7))
• CREATE SERVER (CREATE_SERVER(7))

---

and that's the whole thing bestie, ily, go map some users 🫶💖

— PostgreSQL 17.11, dated 2026, page CREATE USER MAPPING(7). periodt. 💅✨