Ernst Bunders wrote:
> Im adding this to the knowledgebase. From what version up exactly is
> query time being lgged?

I'm not sure, but in 1.7.0 the query is logged with higher priority if the query took 
longer. So,
you can easily configure to only log queries which took a lot of time.

Switching on all query logging can otherwise be unacceptable in a production 
environment, because
this log-file would grow tremendously, and all that logging may damage performance. 
But logging slow
queries only, may be a usefull tool to detect them.


to be precise:
query duration    log-level

0 - 5 s             DEBUG
5 - 30 s            SERVICE
30 - 60 s           INFO
60 - 120 s          WARN
> 120               query would be killed, an ERROR is logged.

The 'TRACE' level remains unused.

In 1.8 these tresholds may become configurable (probably in fractions of the 'maximal' 
time).

The earliest code which I have is a 1.6 CVS checkout, in which query duration is 
logged already (but
all on DEBUG).

Michiel

-- 
Michiel Meeuwissen                  mihxil'
Mediacentrum 140 H'sum                [] ()
+31 (0)35 6772979         nl_NL eo_XX en_US




Reply via email to