| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add new GUC createrole_self_grant. |
| Date: | 2023-01-15 02:19:21 |
| Message-ID: | CAKFQuwYr=ZrZJqgdH4hp=pSu_zp19qjDdC485KdJGz6PQZBd_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sat, Jan 14, 2023 at 6:12 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> While the function owner has their own pg_db_role_setting preference for
> this setting,
>
Should we be pointing out that if the role with CREATEROLE isn't also a
LOGIN role then there is little point to setting createrole_self_grant on
it specifically? Instead this setting should be set for any user that can
SET to the CREATEROLE role but does have a LOGIN attribute.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-15 18:15:11 | pgsql: Make new GENERATED-expressions code more bulletproof. |
| Previous Message | David G. Johnston | 2023-01-15 01:12:24 | Re: pgsql: Add new GUC createrole_self_grant. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2023-01-15 02:38:05 | Re: fixing CREATEROLE |
| Previous Message | Justin Pryzby | 2023-01-15 02:16:28 | [PATCH] pg_restore: use strerror for errors other than ENOENT |