| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: document pg_settings view doesn't display custom options |
| Date: | 2020-10-29 03:38:08 |
| Message-ID: | 55317999-a09e-cb6c-685c-d797d75b021a@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/10/29 3:45, John Naylor wrote:
> On Wed, Oct 28, 2020 at 2:15 PM John Naylor <john(dot)naylor(at)enterprisedb(dot)com <mailto:john(dot)naylor(at)enterprisedb(dot)com>> wrote:
>
> Starting separate threads to keep from cluttering the TODO list thread.
>
> Here's a patch for the subject, as mentioned in
> https://www.postgresql.org/message-id/20201027220555.GS4951%40momjian.us
>
>
> I just realized I introduced a typo, so here's v2.
+ The <structname>pg_settings</structname> view does not display
+ <link linkend="runtime-config-custom">customized options</link>.
This is true until the module that defines the customized options is loaded,
but not after that. No? For example, pg_settings displays
pg_stat_statements.max after pg_stat_statements is loaded.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-10-29 04:00:30 | Re: recovering from "found xmin ... from before relfrozenxid ..." |
| Previous Message | Justin Pryzby | 2020-10-29 02:44:12 | [PATCH] remove pg_archivecleanup and pg_standby |