| From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> | 
|---|---|
| To: | "Y Sidhu" <ysidhu(at)gmail(dot)com> | 
| Cc: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: Parsing VACUUM VERBOSE | 
| Date: | 2007-06-14 21:01:54 | 
| Message-ID: | 1d4e0c10706141401u2ae5ff73x61a86973b13f6133@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
On 6/14/07, Y Sidhu <ysidhu(at)gmail(dot)com> wrote:
> Can anyone share what value they have set log_min_duration_statement to?
It's OT but we use different values for different databases and needs.
On a very loaded database with a lot of complex queries (lots of join
on big tables, proximity queries, full text queries), we use 100 ms.
It logs ~ 300 000 queries. It allows us to detect big regressions or
new queries which are very slow.
On another database where I want to track transaction leaks, I'm
forced to put it to 0ms.
Basically, the answer is: set it to the lowest value you can afford
without impacting too much your performances (and if you use syslog,
use async I/O or send your log to the network).
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Y Sidhu | 2007-06-14 21:34:13 | Re: Parsing VACUUM VERBOSE | 
| Previous Message | Y Sidhu | 2007-06-14 15:30:21 | Re: Parsing VACUUM VERBOSE |