Re: RES: RES: session_user different from current_user after normal login

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Murillo corvino rocha <murillo_corvinorocha(at)hotmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: RES: RES: session_user different from current_user after normal login
Date: 2022-11-18 21:04:49
Message-ID: d3d1136c-10e7-992a-8a53-56a52b02bd0b@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/18/22 12:52, Murillo corvino rocha wrote:
> Could it be the role=group_read_only? The fact that user1 is a member of
> group_read_only is changing current_user variable?

Well role=group_read_only means this:

psql -d database -h host -U user1

effectively becomes:

psql -d database -h host -U user1

log in as user1 then

SET ROLE group_read_only;

which results in

session_user: user1

current_user: group_read_only.

user_1 being a member of group_read_only does not automatically change
the current_user to group_read_only. This happened because it was
explicitly set up do this.

>
> 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
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2022-11-18 21:09:16 Re: Lots of read activity on index only scan
Previous Message Tom Lane 2022-11-18 20:59:46 Re: Lots of read activity on index only scan