| From: | gparc(at)free(dot)fr |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | Lok P <loknath(dot)73(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Users and object privileges maintenance |
| Date: | 2024-02-19 09:36:47 |
| Message-ID: | 1079660266.467418040.1708335407832.JavaMail.zimbra@free.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 18.02.2024 15 :19, Dominique Devienne wrote:
...
...
But you of course can connect only to DBs you have explicit access to. Just beware that before 15, the built-in PUBLIC
role, which all ROLEs are implicitly members of, had implicit access to newly created DBs.
It's still the same concerning default database CONNECT privilege for PUBLIC.
You must confuse with the fact that v15+ removes PUBLIC creation permission on the [ https://www.postgresql.org/docs/15/ddl-schemas.html#DDL-SCHEMAS-PUBLIC | public schema ]
Regards
Gilles
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-02-19 14:07:05 | Re: Partitioning, Identity and Uniqueness (given pg 16 changes) |
| Previous Message | Darryl Green | 2024-02-19 09:13:13 | Re: Partitioning, Identity and Uniqueness (given pg 16 changes) |