Re: Parsing config files in a directory

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing config files in a directory
Date: 2009-10-26 22:30:30
Message-ID: 4AE62306.9000901@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg,

> This actually seems like a bad idea to me.

You write your tool your way, I'll write my tool mine. We'll see which
one works the best in the field.

> Well you're assuming there's only one tool generating this config? We
> have at least two and possibly more. initdb generates an initial set
> of defaults, the user may well run some kind of autotuning program,
> and then they also have variables set by SET PERSISTENT. That's three
> pieces of configuration being edited by different pieces of software.

Well, that's what I'd call a bad idea. Mixing external autotuner which
writes to files with SET PERSISTENT?

--Josh Berkus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-10-26 22:41:47 Re: GROUP BY bug or feature?
Previous Message Jeff Davis 2009-10-26 22:17:20 Re: "toast.fillfactor" is documented but not recognized?