Could it be the role=group_read_only? The fact that user1 is a member of group_read_only is changing current_user variable?
I’m using a clean psql docker container everytime I need to connect to the database, so, I don’t think it’s related to psql.
\drds
List of settings
Role | Database | Settings
--------------+--------------+-----------------------------------
user1 | mydb | role=group_read_only
rdsadmin | rdsadmin | log_min_messages=panic
rdsadmin | | TimeZone=utc +
| | log_statement=all +
| | log_min_error_statement=debug5 +
| | log_min_messages=panic +
| | exit_on_error=0 +
| | statement_timeout=0 +
| | role=rdsadmin +
| | auto_explain.log_min_duration=-1 +
| | temp_file_limit=-1 +
| | search_path=pg_catalog, public +
| | pg_hint_plan.enable_hint=off +
| | default_transaction_read_only=off +
| | default_tablespace=
| rdsadmin | auto_explain.log_min_duration=-1
(4 rows)
Thanks.
Murillo.
Murillo corvino rocha <murillo_corvinorocha@hotmail.com> writes:
> I am just logging in (using psql) and doing the select: SELECT session_user, current_user;
> The PostgreSQL is an AWS RDS 12.12 instance. No script is being executed. No one besides me is connected to the database. Could it be any server level configuration? I’m pretty sure that few configurations were made to this database.
I believe it's possible to do ALTER USER ... SET ROLE ... or
ALTER DATABASE ... SET ROLE ..., which'd produce this sort of
effect. psql's "\drds" metacommand would help remind you of
any such settings. I can't offhand think of any other server-side
configuration that would do it.
regards, tom lane