| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | bt22kawamotok <bt22kawamotok(at)oss(dot)nttdata(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: is_superuser is not documented |
| Date: | 2022-09-18 07:42:42 |
| Message-ID: | e62a363f-f1f5-efbf-9128-fe17c665f4b8@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| Attachment | Content-Type | Size |
|---|---|---|
| add_document_is_superuser_v4.patch | text/plain | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-09-18 07:53:57 | Re: Refactor backup related code (was: Is it correct to say, "invalid data in file \"%s\"", BACKUP_LABEL_FILE in do_pg_backup_stop?) |
| Previous Message | Noah Misch | 2022-09-18 07:13:12 | Re: remove more archiving overhead |