Skip site navigation (1) Skip section navigation (2)

Re: Parsing config files in a directory

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Parsing config files in a directory
Date: 2009-10-28 20:52:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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 Platform Compatibility / 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(at)gregsmith(dot)com Baltimore, MD

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2009-10-28 20:58:11
Subject: Re: Parsing config files in a directory
Previous:From: Robert HaasDate: 2009-10-28 20:29:43
Subject: Re: Parsing config files in a directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group