TRACE: replace default value for time_threshold with 0 rather than 100
----------------------------------------------------------------------
Key: CORE-3676
URL: http://tracker.firebirdsql.org/browse/CORE-3676
Project: Firebird Core
Issue Type: Improvement
Reporter: Pavel Zotov
The value of time_threshold = 100 often brings hardly analyzed results in case
of many 'lightweight' queries.
For instance, most of all requests of replication system (in case of proper
configuration) will not be logged with threshold more than 30-40 ms.
I think that if someone turned trace on, all enabled events should be logged
until time threshold is explicitly set to some non-zero value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
