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

From Sawada Masahiko
Subject Re: Proposal: knowing detail of config files via SQL
Date
Msg-id CAD21AoC=i_51jNrBYzPGUmH4r7Z93LtbxhN851AVc_xSAiWhTw@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: knowing detail of config files via SQL  (Sawada Masahiko <sawada.mshk@gmail.com>)
List pgsql-hackers
On Sat, Jan 31, 2015 at 3:20 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
> On Sat, Jan 31, 2015 at 2:00 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
>> On Sat, Jan 31, 2015 at 4:56 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 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?
>>>
>>
>> Yep, a line number is also needed.
>> The source file and line number would be primary key of pg_file_settings view.
>> I need to change like that.
>>
>
> Attached patch is latest version including following changes.
> - This view is available to super use only
> - Add sourceline coulmn
>
> Also I registered CF app.
>

Sorry, I registered unnecessary (extra) threads to CF app.
How can I delete them?

Regards,

-------
Sawada Masahiko



pgsql-hackers by date:

Previous
From: Sawada Masahiko
Date:
Subject: Re: Proposal: knowing detail of config files via SQL
Next
From: Andres Freund
Date:
Subject: Re: Re: Overhauling our interrupt handling (was Escaping from blocked send() reprised.)