Re: Proposal: knowing detail of config files via SQL
От | Sawada Masahiko |
---|---|
Тема | Re: Proposal: knowing detail of config files via SQL |
Дата | |
Msg-id | CAD21AoDACu70JEVQNKQ5GaJ3CB4qEMUykGv7a4vMCYXBjMkj4g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Proposal: knowing detail of config files via SQL (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Proposal: knowing detail of config files via SQL
|
Список | pgsql-hackers |
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. Regards, ------- Sawada Masahiko
В списке pgsql-hackers по дате отправления: