Re: Proposal: knowing detail of config files via SQL
| От | David Johnston |
|---|---|
| Тема | Re: Proposal: knowing detail of config files via SQL |
| Дата | |
| Msg-id | CAKFQuwbG=LRS14-mxNLmMOY1ORUqrmiCdMryKFX+e1Kqrp=sug@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 |
David G Johnston <david.g.johnston@gmail.com> writes:
> Tom Lane-2 wrote
>> regression=# alter system reset timezone;
>> ALTER SYSTEM
>> regression=# select pg_reload_conf();
> How does someone know that performing the above commands will result in the
> TimeZone setting being changed from Asia/Shanghai to US/Eastern?
Is that a requirement, and if so why? Because this proposal doesn't
guarantee any such knowledge AFAICS.
The proposal provides for SQL access to all possible sources of variable value setting and, ideally, a means of ordering them in priority order, so that a search for TimeZone would return two records, one for postgresql.auto.conf and one for postgresql.conf - which are numbered 1 and 2 respectively - so that in looking at that result if the postgresql.auto.conf entry were to be removed the user would know that what the value is in postgresql.conf that would become active. Furthermore, if postgresql.conf has a setting AND there is a mapping in an #included file that information would be accessible via SQL as well.
David J.
В списке pgsql-hackers по дате отправления: