Re: Parsing config files in a directory - Mailing list pgsql-hackers

From Greg Smith
Subject Re: Parsing config files in a directory
Date
Msg-id alpine.GSO.2.01.0910281635470.25783@westnet.com
Whole thread Raw
In response to Re: Parsing config files in a directory  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Parsing config files in a directory
List 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 by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parsing config files in a directory
Next
From: Robert Haas
Date:
Subject: Re: Parsing config files in a directory