TRACE: add ability for logging only those PLANs that matched to specified list
of patterns (espesially INDEX names)
-------------------------------------------------------------------------------------------------------------------
Key: CORE-3538
URL: http://tracker.firebirdsql.org/browse/CORE-3538
Project: Firebird Core
Issue Type: Improvement
Reporter: Pavel Zotov
currently (in 2.5) we can set up the following filter for DML-statements:
include_filter %(INSERT|UPDATE|DELETE)%
This means that each SQL-statement that consists of any elements from this list
will be logged.
It will be useful if we could specify not only keywords from fixed list (DML or
DDL) that applies to SQL-statement but any name (e.g. name of INDEX) that can
occurs inside the PLAN of query.
For example, this could be look like this in FBTRACE.CONF:
<database ...>
...
include_PLAN_filter %(MY_TABLE_1_IDX_A|MY_TABLE_1_IDX_B|MY_TABLE_2_IDX_R)%
exclude_PLAN_filter %(MY_TABLE_1_IDX_C|MY_TABLE_1_IDX_D|MY_TABLE_2_IDX_W)%
...
</database>
This can significantly reduce size of trace log that must be analyzed (parsed)
if we only interesting about some index: is it used at all or no ?
--
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 of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of 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-d2d-c2
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
