Re: [HACKERS] Uncommenting .conf WAS: Open items

2004-08-06 Thread Tom Lane
Josh Berkus <[EMAIL PROTECTED]> writes: > I think we can work around that. Putting those few parameters in as: > #SORT_LOCALE = {set at compile time, check SHOW} > ... would still be an improvement for the *majority* of parameters, which are > not set at compile time. Okay, if you can live with

Re: [HACKERS] Uncommenting .conf WAS: Open items

2004-08-06 Thread Josh Berkus
Tom, > Wrong on both counts: it's not really minor (if it were, it would have > got done) and you will need to touch the code. See the earlier > discussion. There are several defaults that are presently determined > at compile time and are not correctly reflected into > postgresql.conf.sample.

Re: [HACKERS] Uncommenting .conf WAS: Open items

2004-08-06 Thread Tom Lane
Josh Berkus <[EMAIL PROTECTED]> writes: > I see this as a really minor change that will greatly improve the > comprehension of how to modify the .conf file. It's documentation, really, > and we won't be touching any code. Wrong on both counts: it's not really minor (if it were, it would hav

Re: [HACKERS] Uncommenting .conf WAS: Open items

2004-08-06 Thread Josh Berkus
Bruce, etc: > If you change shared_buffers to 2000, remove the comment and reload, the > variable is now 2000. If you comment out the variable and reload again, > it is still 2000, not the default. And more than one person has been baffled and confused by this, including several major contribut