Re: Proposal: knowing detail of config files via SQL - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Proposal: knowing detail of config files via SQL
Date
Msg-id CA+TgmoYLC_y-zxayYnnYfZ+Zvkegh2sfaDkDW0PmxsOQvtvV2Q@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: knowing detail of config files via SQL  (David Steele <david@pgmasters.net>)
Responses Re: Proposal: knowing detail of config files via SQL
List pgsql-hackers
On Fri, Apr 24, 2015 at 2:40 PM, David Steele <david@pgmasters.net> wrote:
>   <para>
>    The view <structname>pg_file_settings</structname> provides access to
> run-time parameters
>    that are defined in configuration files via SQL.  In contrast to
>    <structname>pg_settings</structname> a row is provided for each
> occurrence
>    of the parameter in a configuration file.  This is helpful for
> discovering why one value
>    may have been used in preference to another when the parameters were
> loaded.
>   </para>

This seems to imply that this gives information about only a subset of
configuration files; specifically, those auto-generated based on SQL
commands - i.e. postgresql.conf.auto.  But I think it's supposed to
give information about all configuration files, regardless of how
generated.  Am I wrong?  If not, I'd suggest "run-time parameters that
are defined in configuration files via SQL" -> "run-time parameters
stored in configuration files".

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Additional role attributes && superuser review
Next
From: David Steele
Date:
Subject: Re: Proposal: knowing detail of config files via SQL