Re: postgresql.conf and postgres options

From: Thomas Swan <tswan-lst(at)ics(dot)olemiss(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, pgsql-doc(at)postgresql(dot)org
Subject: Re: postgresql.conf and postgres options
Date: 2001-01-24 22:09:20
Message-ID: 5.0.2.1.0.20010124160742.02fea1b0@tangent.ics.olemiss.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I think the list is great, show what can be configured rather than
guessing/digging to find it, where it belongs, in what order (if any), etc.
etc. etc.
The only addition I could think would be to label (default value).

Needless, I like it.. :)

At 1/24/2001 01:03 PM, Bruce Momjian wrote:
> > Bruce Momjian writes:
> >
> > > I have added all possible config options to postgresql.conf.sample.
> >
> > It was actually fully intentional that there was *no* list of all possible
> > config options in the sample file, because
> >
> > 1) Who's going to maintain this?
> >
> > 2) People should read the documentation before messing with options.
> >
> > (" is not the correct string delimiter either.)
>
>Changed to ''. Thanks.
>
> >
> > I have bad experiences with sample config files. The first thing I
> > usually do is delete them and dig up the documentation.
> >
> > Do other people have comments on this issue?
>
>I have marked all places where these defaults are set in the C code,
>pointing them to update postgresql.conf.sample.
>
>I found it is nice to see a nice list of all options for quick review.
>It makes the file much more useful, I think.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2001-01-24 22:12:32 Re: WAL documentation
Previous Message Peter Eisentraut 2001-01-24 22:02:09 Permissions on CHECKPOINT