Re: postgresql.conf and postgres options - Mailing list pgsql-hackers

From Thomas Swan
Subject Re: postgresql.conf and postgres options
Date
Msg-id 5.0.2.1.0.20010124160742.02fea1b0@tangent.ics.olemiss.edu
Whole thread Raw
In response to Re: postgresql.conf and postgres options  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: postgresql.conf and postgres options
List 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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Permissions on CHECKPOINT
Next
From: "Oliver Elphick"
Date:
Subject: Re: WAL documentation