password is MD5>-encrypted.
- The remaining variants change a role's session default for
- a specified configuration variable. Whenever the role subsequently
- starts a new session, the specified value becomes the session default,
- overriding whatever setting is present in postgresql.conf>
- or has been received from the postgres command line.
- (For a role without LOGIN> privilege, session defaults have
- no effect.)
- Ordinary roles can change their own session defaults.
- Superusers can change anyone's session defaults.
- Roles having CREATEROLE> privilege can change defaults for
- non-superuser roles.
- Certain variables cannot be set this way, or can only be
+ The remaining variants change a role's session default for a
+ specified configuration variable. Whenever the role subsequently
+ starts a new session, the specified value becomes the session
+ default, overriding whatever setting is present in
+ postgresql.conf> or has been received from the postgres
+ command line. This only happens at login time, so configuration
+ settings associated with a role to which you've
+ linkend="sql-set-role" endterm="sql-set-role-title"> will be ignored.
+ Superusers can change anyone's session defaults. Roles having
+ CREATEROLE> privilege can change defaults for non-superuser
+ roles. Certain variables cannot be set this way, or can only be
set if a superuser issues the command.
the parameter as the role-specific value.
+ Role-specific variable setting take effect only at login;
+
+ does not process role-specific variable settings.
+
+
See
and
linkend="runtime-config"> for more information about allowed
allowed to a later SET ROLE>.
+ SET ROLE> does not process session variables as specified by
+ the role's
+ endterm="sql-alterrole-title"> settings; this only happens during
+ login.
+
+
SET ROLE> cannot be used within a
SECURITY DEFINER> function.