| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: auto_explain WAS: RFC: Timing Events |
| Date: | 2012-11-22 13:03:27 |
| Message-ID: | 20121122130327.GB4316@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Smith escribió:
> If I could just turn off logging just during those
> periods--basically, throwing them away only when some output rate
> throttled component hit its limit--I could still find them in the
> data collected the rest of the time. There are some types of
> problems that also only occur under peak load that this idea would
> miss, but you'd still be likely to get *some* of them,
> statistically.
Uhm, what if you had a simple script that changed postgresql.conf and
SIGHUP'ed postmaster? You could have it turn logging on and off
depending on predefined system load watermarks.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2012-11-22 13:05:56 | Re: PQconninfo function for libpq |
| Previous Message | Amit kapila | 2012-11-22 12:38:42 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |