From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
---|---|
To: | bt22kawamotok <bt22kawamotok(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: is_superuser is not documented |
Date: | 2022-09-09 15:47:37 |
Message-ID: | 190e2a49-5736-4f68-a3ed-e592e263ace6@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Sep 9, 2022, at 2:28 AM, bt22kawamotok wrote:
> is_superuser function checks whether a user is a superuser or not, and
> is commonly used. However, is_superuser is not documented and is set to
> UNGROUPED in guc.c. I think is_superuser should be added to the
> documentation and set to PRESET OPTIONS.What are you thought on this?
There is no such function. Are you referring to the GUC? I agree that it should
be added to the documentation. The main reason is that it is reported by
ParameterStatus along with some other GUCs described in the Preset Options
section.
postgres=# \dfS is_superuser
List of functions
Schema | Name | Result data type | Argument data types | Type
--------+------+------------------+---------------------+------
(0 rows)
postgres=# SHOW is_superuser;
is_superuser
--------------
on
(1 row)
Do you mind writing a patch?
--
Euler Taveira
EDB https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2022-09-09 15:49:48 | Re: Remove redundant code in pl_exec.c |
Previous Message | Tom Lane | 2022-09-09 15:34:19 | Re: Remove redundant code in pl_exec.c |