From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: wishlist: dynamic log volume control |
Date: | 2004-02-19 04:26:05 |
Message-ID: | 200402182126.05061.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday February 18 2004 7:13, Bruce Momjian wrote:
> Martijn van Oosterhout wrote:
> -- Start of PGP signed section.
>
> > On Wed, Feb 18, 2004 at 03:54:39PM -0700, Ed L. wrote:
> > > We extract great value from logging every SQL statement, its
> > > duration, etc., in service to debugging, troubleshooting, monitoring,
> > > etc. But we have a number of clusters that seem to always be bumping
> > > into disk I/O bottlenecks. With a system running at 100 QPS, we're
> > > inclined to quiet the logging and only turn it up as needed (which
> > > will, by definition, be while it was quieted). But many of these
> > > production clusters are not easily restarted; the customer has to be
> > > notified, etc. "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...
> >
> > In any particular session you can do SET log_statement = off or some
> > such. That way you can make logging more fine grained.
>
> You can also change the postgresql.conf file and SIGHUP the postmaster
> for it to take affect. It doesn't restart the server.
Very fast coding, and simply amazing patch distribution. ;-)
Thx.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-19 04:33:01 | Re: wishlist: dynamic log volume control |
Previous Message | Bill Moran | 2004-02-19 02:21:29 | Problems with plpgsql and FOR loops |