| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: knowing detail of config files via SQL |
| Date: | 2015-01-30 19:56:52 |
| Message-ID: | 9869.1422647812@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, Jan 30, 2015 at 12:05 PM, David Fetter <david(at)fetter(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-01-30 20:34:29 | Re: Hot Standby WAL reply uses heavyweight session locks, but doesn't have enough infrastructure set up |
| Previous Message | David Johnston | 2015-01-30 19:12:09 | Re: Proposal: knowing detail of config files via SQL |