| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing config files in a directory |
| Date: | 2009-10-28 16:39:34 |
| Message-ID: | 407d949e0910280939y751615ean33c21330e0a5b650@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 28, 2009 at 7:33 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Greg Smith escribió:
>
>> This sounds familiar...oh, that's right, this is almost the same
>> algorithm pgtune uses. And it sucks,
It's also a blatant violation of packaging rules for Debian if not
every distribution. If you edit the user's configuration file then
there's no way to install a modified default configuration file. You
can't tell the automatic modifications apart from the user's
modifications. So the user will get a prompt asking if he wants the
new config file or to keep his modifications which he never remembered
making.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-10-28 16:44:38 | Re: Parsing config files in a directory |
| Previous Message | Tom Lane | 2009-10-28 16:26:28 | Re: Parsing config files in a directory |