From: | AC Gomez <antklc(at)gmail(dot)com> |
---|---|
To: | Guyren Howe <guyren(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Backing out of privilege grants rabbit hole |
Date: | 2020-04-03 03:42:12 |
Message-ID: | CABtmK-jaaJVT=eBz6-Yti98X2-wSnQQ5GoufWf=nMoJVDudZNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the quick response. The problem is, in most cases the owner is
not the grantee. So if a role, let's say a temp employee, gets grants, then
leaves, I can't do a drop owned because that temp never owned those
objects, he just was granted access. Is there a "drop granted" kind of
thing?
On Thu, Apr 2, 2020, 11:37 PM Guyren Howe <guyren(at)gmail(dot)com> wrote:
> https://www.postgresql.org/docs/12/sql-drop-owned.html
>
> On Apr 2, 2020, at 20:34 , AC Gomez <antklc(at)gmail(dot)com> wrote:
>
> Do I understand correctly that if a role was assigned countless object
> privileges and you want to delete that role you have to sift through a
> myriad of privilege grants in what amounts to a time consuming trial and
> error exercise until you've got them all?
>
> Or is there a single command that with just delete the role and do a
> blanket grant removal at the same time?
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | James Brauman | 2020-04-03 04:42:39 | Improve COPY performance into table with indexes. |
Previous Message | Guyren Howe | 2020-04-03 03:41:02 | Re: Backing out of privilege grants rabbit hole |