| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: wishlist: dynamic log volume control |
| Date: | 2004-02-19 15:21:43 |
| Message-ID: | 200402190821.43471.pgsql@bluepolka.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2004-02-19 15:22:46 | Re: Differences between postgres and mysql |
| Previous Message | Randall Skelton | 2004-02-19 15:08:32 | Inner join question |