Re: Parsing config files in a directory
От | Magnus Hagander |
---|---|
Тема | Re: Parsing config files in a directory |
Дата | |
Msg-id | 9837222c0910240932i7a2046f0gfb1ccf118136d81b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parsing config files in a directory (Grzegorz Jaskiewicz <gj@pointblue.com.pl>) |
Список | pgsql-hackers |
2009/10/24 Grzegorz Jaskiewicz <gj@pointblue.com.pl>: > > On 24 Oct 2009, at 14:41, Magnus Hagander wrote: > >> Per discussion at the developer meeting back in Ottawa, attached is an >> initial patch that implements reading a directory of configuration >> files instead of just one. The idea being that something like a tuning >> tool, or pgadmin, for example can drop and modify files in this >> directory instead of modifying the main config file (which can be very >> hard to machine-parse). The idea is the same as other software like >> apache that parses multiple files. >> >> Files are parsed in alphabetical order so it's predictable, and you >> can make sure some files override others etc. >> >> Comments, before I go do the final polishing? :-) > > I don't know what the discussion topics were, since I was not there. But primary question is, cannot that be achieved withsimple includes in postgresql.conf ? You could, but that would take away the main point - which is that the utilities would once again have to edit and parse postgresql.conf, which is *very* hard to do reliably given that it's a free-format file. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: