| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, nathandbossart(at)gmail(dot)com, steve(at)supabase(dot)io, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Allow placeholders in ALTER ROLE w/o superuser |
| Date: | 2022-11-20 17:50:19 |
| Message-ID: | CAPpHfduy9JHCYWcdxfWqoG=7J_d_MyRZ=bCgmUT1sEyhvyU_pA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
.On Sun, Nov 20, 2022 at 8:48 PM Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> I've drafted a patch implementing ALTER ROLE ... SET ... TO ... USER SET syntax.
>
> These options are working only for USERSET GUC variables, but require
> less privileges to set. I think there is no problem to implement
>
> Also it seems that this approach doesn't conflict with future
> privileges for USERSET GUCs [1]. I expect that USERSET GUCs should be
> available unless explicitly REVOKEd. That mean we should be able to
> check those privileges during ALTER ROLE.
>
> Opinions on the patch draft?
>
> Links
> 1. https://mail.google.com/mail/u/0/?ik=a20b091faa&view=om&permmsgid=msg-f%3A1749871710745577015
Uh, sorry for the wrong link. I meant
https://www.postgresql.org/message-id/2271988.1668807706@sss.pgh.pa.us
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-11-20 19:00:12 | Re: Avoid double lookup in pgstat_fetch_stat_tabentry() |
| Previous Message | Alexander Korotkov | 2022-11-20 17:48:04 | Re: Allow placeholders in ALTER ROLE w/o superuser |