From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Joseph Koshakow <koshy44(at)gmail(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, bt22kawamotok <bt22kawamotok(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: is_superuser is not documented |
Date: | 2023-03-29 21:21:00 |
Message-ID: | ZCSrvEQaA6cl3ZSy@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 2, 2023 at 12:00:43PM -0500, Joseph Koshakow wrote:
>
>
> On Thu, Mar 2, 2023 at 11:53 AM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
> wrote:
> >
> > On 2022/09/14 14:27, bt22kawamotok wrote:
> > > I update patch to reflect master update.
> >
> > Thanks for updating the patch!
> >
> > + <para>
> > + Shows whether the current user is a superuser or not.
> > + </para>
> >
> > How about adding the note about when this parameter can change,
> > like we do for in_hot_standby docs? I applied this change to the patch.
> > Attached is the updated version of the patch.
> >
>
> I just came across this thread and noticed that the patch was never
> merged. There is some brief docs for is_superuser in the SHOW docs:
> https://www.postgresql.org/docs/current/sql-show.html, but the GUC
> fields were never updated.
>
> Is there a reason that it never got merged or was it just forgotten
> about?
Uh, where are you looking? I see it in the SGML, and in the PG 15 docs:
https://www.postgresql.org/docs/current/sql-show.html
IS_SUPERUSER
True if the current role has superuser privileges.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
From | Date | Subject | |
---|---|---|---|
Next Message | Riccardo Gobbo | 2023-03-29 21:29:45 | Images storing techniques |
Previous Message | Daniel Gustafsson | 2023-03-29 20:18:43 | Re: [EXTERNAL] Support load balancing in libpq |