From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: document pg_settings view doesn't display custom options |
Date: | 2020-10-29 12:54:07 |
Message-ID: | CAFBsxsGno8vgXPC5exQXRBTsLQVYB=D4kkdXfnw3t0Jw-WNpbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 28, 2020 at 11:38 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
wrote:
>
>
> 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.
>
True, how about this:
The <structname>pg_settings</structname> does not display
<link linkend="runtime-config-custom">customized options</link>
that have been set before the relevant extension module has been loaded.
--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2020-10-29 13:03:33 | Re: making update/delete of inheritance trees scale better |
Previous Message | Thomas Munro | 2020-10-29 12:20:28 | Re: Collation versioning |