Re: Improving postgresql.conf - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Improving postgresql.conf
Date
Msg-id 87fz8v7344.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Improving postgresql.conf  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgsql-hackers
Andreas Pflug <pgadmin@pse-consulting.de> writes:

> Tom Lane wrote:
> 
> >Andreas Pflug <pgadmin@pse-consulting.de> writes:
> >
> >> How about *requiring* to set any variable, at least to xxx='default'?
> >
> >Don't like that ... we are not in the fascism business here ;-).

It would just make it too hard to add new variables. Nobody would be able to
upgrade without adding those variables to their config files. 

That might make sense for major new features that require hands-on
involvement, but postgres tries to avoid that in favour of having everything
just work without intervention. And you don't want every user to have to
explicitly enable every new feature when upgrading.

Besides, often new variables are just new debugging hooks like
enable_hash_join or such that users shouldn't even have to know about until
they need it.

-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: logfile rotation
Next
From: Andreas Pflug
Date:
Subject: Re: Improving postgresql.conf