set_role(7) [suse man page]

SET 
ROLE(7)							   SQL Commands 						       SET ROLE(7)

NAME

       SET ROLE - set the current user identifier of the current session

SYNOPSIS

       SET [ SESSION | LOCAL ] ROLE rolename
       SET [ SESSION | LOCAL ] ROLE NONE
       RESET ROLE

DESCRIPTION

       This  command sets the current user identifier of the current SQL session to be rolename. The role name can be written as either an identi-
       fier or a string literal.  After SET ROLE, permissions checking for SQL commands is carried out as though the named role were the one  that
       had logged in originally.

       The  specified  rolename must be a role that the current session user is a member of.  (If the session user is a superuser, any role can be
       selected.)

       The SESSION and LOCAL modifiers act the same as for the regular SET [set(7)] command.

       The NONE and RESET forms reset the current user identifier to be the current session user identifier.  These forms can be executed  by  any
       user.

NOTES

       Using  this  command,  it  is  possible	to  either  add privileges or restrict one's privileges. If the session user role has the INHERITS
       attribute, then it automatically has all the privileges of every role that it could SET ROLE to; in this case SET  ROLE	effectively  drops
       all the privileges assigned directly to the session user and to the other roles it is a member of, leaving only the privileges available to
       the named role. On the other hand, if the session user role has the NOINHERITS attribute, SET ROLE drops the privileges	assigned  directly
       to the session user and instead acquires the privileges available to the named role.

       In particular, when a superuser chooses to SET ROLE to a non-superuser role, she loses her superuser privileges.

       SET  ROLE  has  effects comparable to SET SESSION AUTHORIZATION [set_session_authorization(7)], but the privilege checks involved are quite
       different. Also, SET SESSION AUTHORIZATION determines which roles are allowable for later SET ROLE commands, whereas  changing  roles  with
       SET ROLE does not change the set of roles allowed to a later SET ROLE.

       SET ROLE does not process session variables as specified by the role's ALTER ROLE [alter_role(7)] settings; this only happens during login.

       SET ROLE cannot be used within a SECURITY DEFINER function.

EXAMPLES

       SELECT SESSION_USER, CURRENT_USER;

	session_user | current_user
       --------------+--------------
	peter	     | peter

       SET ROLE 'paul';

       SELECT SESSION_USER, CURRENT_USER;

	session_user | current_user
       --------------+--------------
	peter	     | paul

COMPATIBILITY

       PostgreSQL allows identifier syntax ("rolename"), while the SQL standard requires the role name to be written as a string literal. SQL does
       not allow this command during a transaction; PostgreSQL does not make this restriction because there is no  reason  to.	 The  SESSION  and
       LOCAL modifiers are a PostgreSQL extension, as is the RESET syntax.

SEE ALSO

       SET SESSION AUTHORIZATION [set_session_authorization(7)]

SQL - Language Statements					    2010-05-14							       SET ROLE(7)

Check Out this Related Man Page

SET SESSION 
AUTHORIZATION(7)					   SQL Commands 				      SET SESSION AUTHORIZATION(7)

NAME

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

SYNOPSIS

       SET [ SESSION | LOCAL ] SESSION AUTHORIZATION username
       SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
       RESET SESSION AUTHORIZATION

DESCRIPTION

       This  command  sets the session user identifier and the current user identifier of the current SQL-session context to be username. The user
       name may be written as either an identifier or a string literal.  The session user identifier is valid for the duration	of  a  connection;
       for example, it is possible to temporarily become an unprivileged user and later switch back to become a superuser.

       The  session user identifier is initially set to be the (possibly authenticated) user name provided by the client. The current user identi-
       fier is normally equal to the session user identifier, but may change temporarily in the context of ``setuid'' functions and similar mecha-
       nisms. The current user identifier is relevant for permission checking.

       The  session  user  identifier may be changed only if the initial session user (the authenticated user) had the superuser privilege. Other-
       wise, the command is accepted only if it specifies the authenticated user name.

       The SESSION and LOCAL modifiers act the same as for the regular SET [set(7)] command.

       The DEFAULT and RESET forms reset the session and current user identifiers to be the originally authenticated user name.  These	forms  are
       always accepted.

EXAMPLES

       SELECT SESSION_USER, CURRENT_USER;
	current_user | session_user
       --------------+--------------
	peter	     | peter

       SET SESSION AUTHORIZATION 'paul';

       SELECT SESSION_USER, CURRENT_USER;
	current_user | session_user
       --------------+--------------
	paul	     | paul

COMPATIBILITY

       SQL99

       SQL99 allows some other expressions to appear in place of the literal username which are not important in practice. PostgreSQL allows iden-
       tifier syntax ("username"), which SQL does not. SQL does not allow this command	during	a  transaction;  PostgreSQL  does  not	make  this
       restriction  because  there  is no reason to. The privileges necessary to execute this command are left implementation-defined by the stan-
       dard.

SQL - Language Statements					    2001-04-21					      SET SESSION AUTHORIZATION(7)

Linux and UNIX Man Pages

set_role(7) [suse man page]

Check Out this Related Man Page