From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: wishlist: dynamic log volume control |
Date: | 2004-02-19 16:13:32 |
Message-ID: | 200402191613.i1JGDWn22512@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ed L. wrote:
> On Wednesday February 18 2004 9:33, Tom Lane wrote:
> > "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > > "It'd be nice" if we
> > > could adjust the volume of logging dynamically (i.e., turn-off of
> > > statement logging, etc) without have to restart the server...
> >
> > Why do you think you need to restart the server? Adjust postgresql.conf
> > and SIGHUP the postmaster.
>
> Well, on closer look, there it is in plain sight in the runtime config
> documentation I've looked through a hundred times for other purposes. Just
> one of many features I haven't discovered, I guess.
>
> The 7.3.4 doc (doc/html/runtime-config.html) does say the log_connections
> option can only be set at server start or in the postgresql.conf
> configuration file. That seems a little ambiguous on the SIGHUP'ability of
> that option. My 7.3.4 install here shows all the log_* options are
> dynamically reloadable.
The issue is that you can't set log_connections from psql. Should we
improve the doc wording?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-02-19 16:26:09 | Re: PostgreSQL on Windows |
Previous Message | Denny Morais | 2004-02-19 15:50:13 | Edit Tables... |