| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Granting control of SUSET gucs to non-superusers |
| Date: | 2021-05-03 18:48:04 |
| Message-ID: | 3836367.1620067684@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> One thing that seems missing from this discussion and is part of what
> paused my effort on the 'admin' role proposed towards the end of the
> last cycle is that we really need to consider how this all plays with
> ALTER SYSTEM and not just SUSET GUCs but also other (eg: POSTMASTER,
> SIGHUP) GUCs.
Yeah, I'd meant to bring that up too. The ability to use ALTER
SYSTEM freely is probably a much bigger use-case than messing with
SUSET variables within one's own session.
I'm still of the opinion that slicing and dicing this at the per-GUC
level is a huge waste of effort. Just invent one role that lets
grantees set any GUC, document it as being superuser-equivalent,
and be done.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-05-03 18:50:28 | Re: Granting control of SUSET gucs to non-superusers |
| Previous Message | Peter Geoghegan | 2021-05-03 18:43:08 | Re: MaxOffsetNumber for Table AMs |