From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: wishlist: dynamic log volume control |
Date: | 2004-02-19 02:13:18 |
Message-ID: | 200402190213.i1J2DIk20575@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
--
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 | Bill Moran | 2004-02-19 02:21:29 | Problems with plpgsql and FOR loops |
Previous Message | Dirk Olbertz | 2004-02-19 00:44:22 | Big Tables vs. many Tables vs. many Databases |