Re: is_superuser is not documented

From: Joseph Koshakow <koshy44(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: 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-02 17:00:43
Message-ID: CAAvxfHdLRJerbg0j1EPifA3PY9iMs8-BZEGYjFr8O1i5nRdtTg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

- Joe Koshakow

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-03-02 17:04:27 Re: Making empty Bitmapsets always be NULL
Previous Message gkokolatos 2023-03-02 16:34:23 Re: Add LZ4 compression in pg_dump