From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Justin Clift <justin(at)postgresql(dot)org>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_config : postgresql.conf adjustments? |
Date: | 2002-09-29 16:34:45 |
Message-ID: | Pine.LNX.4.33.0209291225550.15588-100000@polluelo.lab.protecne.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 29 Sep 2002, Tom Lane wrote:
> Justin Clift <justin(at)postgresql(dot)org> writes:
> > Would it be beneficial for us to extend "pg_config" to update the
> > postgresql.conf file?
>
> This seems far outside pg_config's charter. It is a simple
> information reporter that can be run by anybody. Making it able
> to mess with (or even look at) postgresql.conf introduces a host
> of permissions problems and logistical issues.
>
> I don't really see what's wrong with using a text editor anyway ;-)
Obviously he wants a tool that allows setting parameters from a shell
script or something for use within pg_autotune. I don't see why it is
bad to have a tool to do this; if someone can use it (and modify
postgresql.conf) obviously he has permission to read (and write)
postgresql.conf.
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Hoy es el primer dia del resto de mi vida"
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2002-09-29 17:02:25 | Re: DROP COLUMN misbehaviour with multiple inheritance |
Previous Message | Hannu Krosing | 2002-09-29 16:33:48 | Re: DROP COLUMN misbehaviour with multiple inheritance |