Re: document pg_settings view doesn't display custom options

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: document pg_settings view doesn't display custom options
Date: 2020-10-30 16:07:11
Message-ID: 95743.1604074031@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

John Naylor <john(dot)naylor(at)enterprisedb(dot)com> writes:
> On Thu, Oct 29, 2020 at 11:51 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
> wrote:
>> Also I think this note should be in the different paragraph from the
>> paragraph
>> of "The pg_settings view cannot be inserted into or deleted from...."
>> because
>> they are different topics. Thought?

> Agreed on both points. In a separate paragraph, I think it's awkward to
> start two consecutive sentences with "The pg_settings view". If we put it
> in the previous paragraph we could phrase it like this:

> "See Section 20.1 for more information about the various ways to change
> these parameters. Customized options are not displayed until the
> extension module that defines them has been loaded.

That just moves the subject-inconsistency to a different para :-(
I think this item should be its own new para.

As for the repetitiveness, we could just say "This view ...", in one or
even both paras.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Georgios Kokolatos 2020-10-30 16:09:21 Re: pg_upgrade analyze script
Previous Message Georgios Kokolatos 2020-10-30 16:01:27 Re: Extending range type operators to cope with elements