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)
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Hoy es el primer dia del resto de mi vida"
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2002-09-29 17:02:25|
|Subject: Re: DROP COLUMN misbehaviour with multiple inheritance |
|Previous:||From: Hannu Krosing||Date: 2002-09-29 16:33:48|
|Subject: Re: DROP COLUMN misbehaviour with multiple inheritance|