From: | Edwin UY <edwin(dot)uy(at)gmail(dot)com> |
---|---|
To: | soroush jurat <srsh(dot)jurat(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: GRANT CONNECT ON DATABASE |
Date: | 2024-06-10 00:27:29 |
Message-ID: | CA+wokJ_go6xvLCTBNyNC_CVfYXGyZ8qkV26X5r7LhTB2+odFMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks. Yeah, the ALTER fixed it.
I thought the CONNECT should have done the same thing.
Is the GRANT CONNECT not necessary then?
On Mon, Jun 10, 2024 at 12:14 PM soroush jurat <srsh(dot)jurat(at)gmail(dot)com> wrote:
> To grant the role login access, you need to modify the role to have the
> LOGIN attribute. You can do this by running the following command:
>
> ALTER ROLE [blah] WITH LOGIN;
>
>
>
> On Sun, 9 Jun 2024 at 20:09 Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> A role was created as below:
>> CREATE ROLE [blah] WITH NOLOGIN NOSUPERUSER INHERIT NOCREATEDB
>> NOCREATEROLE NOREPLICATION VALID UNTIL 'infinity';
>>
>> Doesn't the following SQLs supposed to give the role login access?
>>
>> ALTER ROLE [blah] WITH ENCRYPTED PASSWORD 'blahpassword' ;
>> GRANT CONNECT ON DATABASE [blahdb] TO [blahuser] ;
>>
>> We're trying to take the minimalist approach for a user access to have
>> access to only the tables he has created and only to a specific database
>> and schema.
>>
>> Regards,
>> Ed
>>
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-06-10 00:30:30 | Re: GRANT CONNECT ON DATABASE |
Previous Message | David G. Johnston | 2024-06-10 00:27:16 | Re: GRANT CONNECT ON DATABASE |