| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas |
| Date: | 2022-11-30 22:57:20 |
| Message-ID: | CAMsGm5fGPACXaWajuh4EqoaDuf4Z_3Z7qf+BDzDENN8-FH1iGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, 30 Nov 2022 at 17:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
BTW, is "create a schema with the same name" sufficient detail?
> You have to either make it owned by that user, or explicitly
> grant CREATE permission on it. I'm not sure if that detail
> belongs here, but it feels like maybe it does.
It might be worth mentioning AUTHORIZATION. The easiest way to create an
appropriately named schema for a user is "CREATE SCHEMA AUTHORIZATION
username".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-11-30 22:58:36 | Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas |
| Previous Message | Tom Lane | 2022-11-30 22:35:01 | Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-11-30 22:58:36 | Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas |
| Previous Message | Tom Lane | 2022-11-30 22:35:01 | Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas |