ALTER_USER_MAPPING(7pg16)

πŸ“¦ version 16.15, in opensuse-leap 16.0

πŸ’– NAME

ALTER_USER_MAPPING(7pg16) β€” change the definition of a user mapping. Okay so this is the ALTER USER MAPPING(7) page from the PostgreSQL 16.15 docs, bestie, and it's literally here to help you tweak a user mapping without spiraling. ✨

✨ SYNOPSIS ✨

ALTER USER MAPPING FOR { user_name | USER | CURRENT_ROLE | CURRENT_USER | SESSION_USER | PUBLIC }
    SERVER server_name
    OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )

🌸 DESCRIPTION 🌸

Girl, ALTER USER MAPPING changes the definition of a user mapping. That's the whole vibe. πŸ’…

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

πŸŽ€ PARAMETERS πŸŽ€

  • user_name β€” the 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. all of them, no cap.
  • server_name β€” the server name of the user mapping.
  • OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] ) β€” change options for the user mapping. The new options override any previously specified options. ADD, SET, and DROP specify the action to be performed. ADD is assumed if no operation is explicitly specified. Option names must be unique; options are also validated by the server's foreign-data wrapper.

πŸ¦‹ EXAMPLES πŸ¦‹

Change the password for user mapping bob, server foo:

ALTER USER MAPPING FOR bob SERVER foo OPTIONS (SET password 'public');

🌈 COMPATIBILITY 🌈

ALTER USER MAPPING conforms to ISO/IEC 9075-9 (SQL/MED). There is a subtle syntax issue: The standard omits the FOR key word. Since both CREATE USER MAPPING and DROP USER MAPPING use FOR in analogous positions, and IBM DB2 (being the other major SQL/MED implementation) also requires it for ALTER USER MAPPING, PostgreSQL diverges from the standard here in the interest of consistency and interoperability.

πŸ‘‘ SEE ALSO πŸ‘‘


That's the whole glow-up, bestie. Source/version: PostgreSQL 16.15. Date: 2026. Manual title: ALTER USER MAPPING(7) β€” slay. πŸ’–

πŸ“¦ where this page comes from