Re: set role issue

From: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: set role issue
Date: 2025-08-04 15:23:08
Message-ID: CAA5-nLByWL++=WZEC52Espbgd6k4O27RO3b+wEBKaTkrL2bquw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you for clarifying this point.
And yes of course grantor, sorry for the confusion.

Regards,

Fabrice

On Mon, Aug 4, 2025 at 4:30 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Fabrice Chapuis <fabrice636861(at)gmail(dot)com> writes:
> > I do the following command when connecting locally with user postgres
> > SET ROLE asuperrole; -- asuperrole has superuser privilege
> > GRANT SELECT ON pg_statistic TO test_role;
>
> > why the grantee is postgres?
>
> You mean "grantor", no? When a superuser does grant/revoke on some
> object, it's recorded as though the object owner issued the command.
> And postgres is the owner of the pg_statistic table.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-08-04 15:24:48 Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events
Previous Message Fujii Masao 2025-08-04 15:18:16 Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid