From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 18:40:32 |
Message-ID: | Pine.LNX.4.33.0402191140150.7005-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 19 Feb 2004, Ed L. wrote:
> 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.
The basic info is there, but not in a table. That would come in quite
handy...
From | Date | Subject | |
---|---|---|---|
Next Message | V i s h a l Kashyap @ [Sai Hertz And Control Systems] | 2004-02-19 18:46:56 | Re: backup and restore questions |
Previous Message | Al Hulaton | 2004-02-19 18:28:43 | Re: book for postgresql |