From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "Ing(dot) Marijo Kristo" <marijo(dot)kristo(at)icloud(dot)com>, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Re: Re: Revoke Connect Privilege from Database not working |
Date: | 2025-04-07 16:06:17 |
Message-ID: | 3467676.1744041977@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-sql |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On master, confirmed that after this command the privilege:
> test_user=c/test_admin (on database testdb) still exists. That seems like
> a bug. Its at least a POLA violation and I cannot figure out how to read
> the revoke reference page in a way that explains it.
I believe what's going on there is explained by the rule that
"grants and revokes done by a superuser are done as if issued
by the object owner". So here, what would be revoked is
test_user=c/postgres, which isn't the privilege at issue.
Include GRANTED BY in the REVOKE to override the default
choice of grantor.
IIRC, said rule was invented before we had the GRANTED BY
syntax. It probably doesn't make as much sense today,
but I'd be very afraid of breaking peoples' work flows
by changing it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2025-04-07 16:22:45 | Re: Re: Re: Revoke Connect Privilege from Database not working |
Previous Message | David G. Johnston | 2025-04-07 15:37:43 | Re: Re: Re: Revoke Connect Privilege from Database not working |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2025-04-07 16:22:45 | Re: Re: Re: Revoke Connect Privilege from Database not working |
Previous Message | David G. Johnston | 2025-04-07 15:37:43 | Re: Re: Re: Revoke Connect Privilege from Database not working |