On Tue, Feb 19, 2008 at 11:11:05AM -0500, Aidan Van Dyk wrote:
> * Csaba Nagy <[EMAIL PROTECTED]> [080219 10:59]:
> > > Are you suggesting we keep appending? So if I set the same parameter 100
> > > times, it would show up on 100 rows?
> >
> > What about not touching the config file at all, but write to a separate
> > file which is completely under the control of postgres and include that
> > at the end of the config file ? You just said includes are a new feature
> > which could complicate things, so why not use it actually in your
> > advantage ;-)
> >
> > That way disabling the overrides would be as simple as commenting out
> > the inclusion of the postgres controlled config file. And it would
> > separate the user writable and machine writable configuration...
>
> Yes, I think that would be necessary (like I said), because in most
> installations, I don't even thing the postgres user even has write
> access to the main config file.
The postgres user gets it by default whenever you run a standard initdb,
AFAIK.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
