Re: privileges oddity

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: privileges oddity
Date: 2020-08-07 18:17:30
Message-ID: 1ceb2a2f-50a0-ef7c-1849-6fa75dd61d64@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/7/20 10:39 AM, Scott Ribe wrote:
>> On Aug 7, 2020, at 11:31 AM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>>
>> Wondering if there's a code path somewhere that lets the default take precedence???
>
> So, I changed the defaults, now I see akanzler=arwdDxt/srv_risk, problem persists
>

Well if this for the same line as before it represents table privileges.
The problem is with schema access. Continuing grasping at straws:

select * from pg_roles where rolname = 'aakanzler';

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Ribe 2020-08-07 18:25:43 Re: privileges oddity
Previous Message Scott Ribe 2020-08-07 17:39:10 Re: privileges oddity