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

From Tom Lane
Subject Re: Proposal: knowing detail of config files via SQL
Date
Msg-id 9869.1422647812@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal: knowing detail of config files via SQL  (David Johnston <david.g.johnston@gmail.com>)
Responses Re: Proposal: knowing detail of config files via SQL
List pgsql-hackers
David Johnston <david.g.johnston@gmail.com> writes:
> On Fri, Jan 30, 2015 at 12:05 PM, David Fetter <david@fetter.org> wrote:
>> Why might the contents of pg_settings be different from what would be
>> in pg_file_settings, apart from the existence of this column?

> ​​The contents of pg_settings uses the setting name as a primary key.
> The contents of pg_file_setting uses a compound key consisting of the
> setting name and the source file.

[ raised eyebrow... ]  Seems insufficient in the case that multiple
settings of the same value occur in the same source file.  Don't you
need a line number in the key as well?
        regards, tom lane



pgsql-hackers by date:

Previous
From: David Johnston
Date:
Subject: Re: Proposal: knowing detail of config files via SQL
Next
From: Andres Freund
Date:
Subject: Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up