ALTER USER MAPPING
ALTER USER MAPPING — change the definition of a user mapping
Synopsis
ALTER USER MAPPING FOR {user_name | USER | CURRENT_ROLE | CURRENT_USER | SESSION_USER | PUBLIC } SERVERserver_name OPTIONS ( [ ADD | SET | DROP ]option ['value'] [, ... ] )Description
ALTER USER MAPPING changes the definition of a user mapping.
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 ifUSAGE privilege on the server has been granted to the user.
Parameters
user_nameUser name of the mapping.
CURRENT_ROLE,CURRENT_USER, andUSERmatch the name of the current user.PUBLICis used to match all present and future user names in the system.server_nameServer 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, andDROPspecify the action to be performed.ADDis 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 mappingbob, serverfoo:
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 theFOR key word. Since bothCREATE USER MAPPING andDROP USER MAPPING useFOR in analogous positions, and IBM DB2 (being the other major SQL/MED implementation) also requires it forALTER USER MAPPING, Postgres Pro diverges from the standard here in the interest of consistency and interoperability.