From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: A smaller default postgresql.conf |
Date: | 2008-08-20 14:33:07 |
Message-ID: | 29088.1219242787@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> # foobar: Adjusts the foobariness of the database
> #
> # This uses units of baz from 1-10, with 10 being the strongest
> #
> # Changing this setting requires a reload
> # This setting may also be changed per session
> # The default value is 5
> #
> # For more information, please see:
> # http://postgres.org/doc/foobar.html
> foobar: 7
So your plan is that postgresql.conf will be approximately two thousand
lines long, before the user has ever touched it at all? (Two hundred
or so GUC variables and ten lines of comments for each one)
This seems entirely nuts. Duplicating the whole contents of config.sgml
in another place is pointless as well as maintenance-intensive. And it
*still* wouldn't be enough information for people to know how to twiddle
many of the variables; there are other parts of the SGML docs that
contain relevant info as well.
I could see having *one* comment at the top of the file giving pointers
to where to read the documentation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-08-20 14:34:20 | Re: make dist does not work in VPATH |
Previous Message | Robert Treat | 2008-08-20 14:31:53 | Re: A smaller default postgresql.conf |