NAME
ALTER_USER_MAPPING - change the definition of a user mapping
SYNOPSIS
ALTER USER MAPPING FOR { \nuser_name\n | USER | CURRENT_ROLE | CURRENT_USER | SESSION_USER | PUBLIC }
\n
SERVER \nserver_name\n
\n
OPTIONS ( [ ADD | SET | DROP ] \noption\n ['\nvalue\n'] [, ... ] )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 if USAGE privilege on the server has been granted to the user.
PARAMETERS
user_name
server_name
OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
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
CREATE USER MAPPING (CREATE_USER_MAPPING(7)), DROP USER MAPPING (DROP_USER_MAPPING(7))