| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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:45:19 |
| Message-ID: | 200402190945.19721.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday February 19 2004 9:13, Bruce Momjian wrote:
> >
> > 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?
Ah, I had no idea that was the issue. Maybe a quick reference
table in the docs would be helpful:
Option SET option Reloads on SIGHUP
=====================================================
shared_buffers no no
log_connections no yes
log_statement yes yes
...
Maybe it's already in there somewhere, I dunno.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2004-02-19 16:48:40 | Re: Big Tables vs. many Tables vs. many Databases |
| Previous Message | Lincoln Yeoh | 2004-02-19 16:41:11 | Re: Need help with postgresql/apache/php optimisation |