| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Overhauling GUCS |
| Date: | 2008-05-31 21:34:27 |
| Message-ID: | 0315F14C-DDE3-47AA-A76E-B04B0430464D@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 31, 2008, at 12:36, Gregory Stark wrote:
> What this sounds like is a sly way to try to get rid of
> postgresql.conf
> entirely and replace it with parameters stored in the database so
> admins would
> adjust the parameters using an SQL syntax rather than a text file.
>
> There are pros and cons of such a system but I think for newbie
> admins that
> would be a thousand times *more* baffling. You would have to learn new
> commands and have no holistic view of what parameters had been set,
> what
> related parameters might exist. You also have no way to keep the
> file in a
> version control system or sync across servers etc.
FWIW, this has not been a barrier to MySQL adoption.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-05-31 22:32:51 | Re: Overhauling GUCS |
| Previous Message | Gregory Stark | 2008-05-31 19:36:54 | Re: Overhauling GUCS |