Movatterモバイル変換

SET SESSION AUTHORIZATION

SET SESSION AUTHORIZATION — set the session user identifier and the current user identifier of the current session

Synopsis

SET [ SESSION | LOCAL ] SESSION AUTHORIZATIONuser_nameSET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULTRESET SESSION AUTHORIZATION

Description

This command sets the session user identifier and the current user identifier of the current SQL session to beuser_name. The user name can be written as either an identifier or a string literal. Using this command, it is possible, for example, to temporarily become an unprivileged user and later switch back to being a superuser.

The session user identifier is initially set to be the (possibly authenticated) user name provided by the client. The current user identifier is normally equal to the session user identifier, but might change temporarily in the context ofSECURITY DEFINER functions and similar mechanisms; it can also be changed bySET ROLE. The current user identifier is relevant for permission checking.

The session user identifier can be changed only if the initial session user (theauthenticated user) has the superuser privilege. Otherwise, the command is accepted only if it specifies the authenticated user name.

TheSESSION andLOCAL modifiers act the same as for the regularSET command.

TheDEFAULT andRESET forms reset the session and current user identifiers to be the originally authenticated user name. These forms can be executed by any user.

Notes

SET SESSION AUTHORIZATION cannot be used within aSECURITY DEFINER function.

Examples

SELECT SESSION_USER, CURRENT_USER; session_user | current_user--------------+-------------- peter        | peterSET SESSION AUTHORIZATION 'paul';SELECT SESSION_USER, CURRENT_USER; session_user | current_user--------------+-------------- paul         | paul

Compatibility

The SQL standard allows some other expressions to appear in place of the literaluser_name, but these options are not important in practice.Postgres Pro allows identifier syntax ("username"), which SQL does not. SQL does not allow this command during a transaction;Postgres Pro does not make this restriction because there is no reason to. TheSESSION andLOCAL modifiers are aPostgres Pro extension, as is theRESET syntax.

The privileges necessary to execute this command are left implementation-defined by the standard.

See Also