On Sat, Jan 31, 2015 at 2:00 PM, Sawada Masahiko <sawada.m...@gmail.com> wrote: > On Sat, Jan 31, 2015 at 4:56 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> David Johnston <david.g.johns...@gmail.com> writes: >>> On Fri, Jan 30, 2015 at 12:05 PM, David Fetter <da...@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. Regards, ------- Sawada Masahiko
000_pg_file_settings_view_v2.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
