Re: .conf File Organization

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: .conf File Organization
Date: 2007-06-12 19:49:06
Message-ID: 200706121249.06313.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom,

> Do you have a better organizing principle than what's there now?

It's mostly detail stuff: putting VACUUM and Autovac together, breaking up
some subsections that now have too many options in them into grouped.

Client Connection Defaults has somehow become a catchall secton for *any*
USERSET variable, regardless of purpose. I'd like to trim it back down and
assign some of those variables to appropriate sections.

On the more hypothetical basis I was thinking of adding a section at the top
with the 7-9 most common options that people *need* to set; this would make
PostgreSQL.conf much more accessable but would result in duplicate options
which might cause some issues.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-06-12 19:51:46 Re: .conf File Organization
Previous Message Gregory Stark 2007-06-12 19:32:06 Re: Selecting a constant question

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-06-12 19:51:46 Re: .conf File Organization
Previous Message Tom Lane 2007-06-12 19:12:37 Re: Two aesthetic bugs in the 1-byte packed varlena code