Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> > No reason Greg can't do it if he wants to ... but the .sample file
> > itself is certainly not all that needs changing.
>
> No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> No reason Greg can't do it if he wants to ... but the .sample file
> itself is certainly not all that needs changing.
No problem. I didn't expect the patch to pass as is, just wanted
to get my foot in the door. :)
- --
Greg Sabino Mullane [EM
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Uh, it is my understanding that all lines can't be uncommented. Some of
> the lines have defaults that are computed, like fsync_method.
Yes, fsync_method shouldn't be uncommented unless you're prepared to put
in the same default value presently computed
Uh, it is my understanding that all lines can't be uncommented. Some of
the lines have defaults that are computed, like fsync_method.
Anyway, we are too busy to consider this for 7.5 unless someone wants to
research all these issues.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message
I know we never reached a full consensus on hackers about the
full solution to the postgresql.conf file, but I think everyone
agreed that having commented-out "default" values was a bad thing,
