From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: DROP ROLE as SUPERUSER |
Date: | 2025-04-29 15:31:44 |
Message-ID: | 1031764.1745940704@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> On Fri, Feb 21, 2025 at 3:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> DROP OWNED also removes relevant permission entries (which can be
>> thought of as things owned by the role, if you hold your head at
>> the right angle). See its man page.
> Except when it doesn't... I'm doing the DROP OWNED, and I'm getting
> several "WARNING: no privileges could be revoked for ..." for SCHEMAs
> and ROUTINEs. (which BTW break my unit tests, which monitor outputs).
[ shrug... ] With no details, it's impossible to comment on this.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Ferrari | 2025-04-30 11:14:29 | alter system appending to a value |
Previous Message | David G. Johnston | 2025-04-29 15:29:28 | Re: Upsert error "column reference is ambiguous" |