Re: Parsing config files in a directory

Поиск
Список
Период
Сортировка
От Greg Smith
Тема Re: Parsing config files in a directory
Дата
Msg-id alpine.GSO.2.01.0910281635470.25783@westnet.com
обсуждение исходный текст
Ответ на Re: Parsing config files in a directory  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Parsing config files in a directory  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Wed, 28 Oct 2009, Robert Haas wrote:

> It would be completely logical to break up the configuration file into
> subfiles by TOPIC.  That would complicate things for tool-writers
> because they would need to get each setting into the proper file, and
> we currently don't have any infrastructure for that.

Already done:

# select name,category from pg_settings limit 1;       name       |                             category
------------------+------------------------------------------------------------------- add_missing_from | Version and
PlatformCompatibility / Previous 
 
PostgreSQL Versions

You could make one per category, and pgtune for example already knows all 
this info.  The somewhat arbitrary category assignments Josh put things 
into are what Peter was complaining about upthread.  Questions like "is 
'effective_cache_size' a memory parameters or an optimizer one?" show why 
this is not trivial to do well.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Parsing config files in a directory
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Parsing config files in a directory