Justin Clift writes:
Would it be beneficial for us to extend pg_config to update the
postgresql.conf file?
That has nothing to do with pg_config's functions.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe
Peter Eisentraut wrote:
Justin Clift writes:
Would it be beneficial for us to extend pg_config to update the
postgresql.conf file?
That has nothing to do with pg_config's functions.
At present, sure. Was thinking a tool for command line changes of
postgresql.conf parameters would be
Justin Clift [EMAIL PROTECTED] 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)
On Sun, 29 Sep 2002, Tom Lane wrote:
Justin Clift [EMAIL PROTECTED] 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
Alvaro Herrera wrote:
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)
Joe Conway wrote:
Alvaro Herrera wrote:
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
Hi all,
Would it be beneficial for us to extend pg_config to update the
postgresql.conf file?
i.e.
pg_config --sort_mem 16384 --shared_buffers 800
pg_config -d /some/datadir --sort_mem 16384 --shared_buffers 800
etc?
Not sure if it should trigger a restart of postmaster, etc, but the
