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 mess
Bruce Momjian wrote:
> I have added all possible config options to postgresql.conf.sample.
> I have attached the new version of the file. I think you will be amazed
> at how GUC gives us such powerful control over PostgreSQL.
Good. As a sysadmin I _like_ sample configs (which I usually rename
> 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 docum
I have added all possible config options to postgresql.conf.sample.
I have attached the new version of the file. I think you will be amazed
at how GUC gives us such powerful control over PostgreSQL.
Thanks, Peter.
> Oliver Elphick writes:
>
> > 2. The following command line options to postgr
I think all valid options should appear in the options file. Right now,
only a few are in there, I think.
> I've just been looking through the options which can and cannot be set in
> postgresql.conf and have a few points to raise.
>
> 1. There are some undocumented options which appear to re
Oliver Elphick writes:
> 2. The following command line options to postgres don't have an equivalent in
> postgresql.conf. Is that intentional? (I suppose it is in several cases,
> and I have left out some where it is obviously intentional.) I can't see
> why these items can't be p
> 1. There are some undocumented options which appear to relate to WAL:
...
> Is there any text anywhere to explain what these do?
> (Point me to that or some commented code, and I'll write
> a documentation patch.)
I'll send description to you soon, thanks.
Vadim
I've just been looking through the options which can and cannot be set in
postgresql.conf and have a few points to raise.
1. There are some undocumented options which appear to relate to WAL:
NameVariableDefault Set by
checkpoint_time
