Re: "set role" semantics - Mailing list pgsql-general

From Adrian Klaver
Subject Re: "set role" semantics
Date
Msg-id 4d1ff0c5-7326-366e-1f1e-8851ea6de3d0@aklaver.com
Whole thread Raw
In response to Re: "set role" semantics  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-general
On 11/9/22 10:55 AM, Bryn Llewellyn wrote:
>> adrian.klaver@aklaver.com <mailto:rian.klaver@aklaver.com> wrote:
>>

>> Revoking PUBLIC has been explained before to you (Bryn Llewellyn).
>>
>> A quick search:
>>
>> https://www.postgresql.org/message-id/2176817.1644613186@sss.pgh.pa.us 
>> <https://www.postgresql.org/message-id/2176817.1644613186@sss.pgh.pa.us>
>>
>> https://www.postgresql.org/message-id/CAKFQuwayij%3DAQRQxJhFuJ3Qejq3E-PfiBjJ9CoHx_L_46BEgXQ@mail.gmail.com
>>
>> https://www.postgresql.org/message-id/CAKFQuwZVq-LerGMTN0E3_7MqhJwtuJuzf0GSnKG32mH_Qf24Zw@mail.gmail.com
> 
> Here's an extract from the script that I copied in my first email:
> 
> *create database d1;
> revoke all on database d1 from public;
> 
> create database d2;
> revoke all on database d2 from public;
> *

Should have added to previous post I missed this on initial read of 
original post.

> 
> Didn't I do exactly what you both said that I failed to do?



-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: "set role" semantics
Next
From: "David G. Johnston"
Date:
Subject: Re: "set role" semantics