Adding the ability to trace (using fbtrace) server access to system tables
--------------------------------------------------------------------------
Key: CORE-6020
URL: http://tracker.firebirdsql.org/browse/CORE-6020
Project: Firebird Core
Issue Type: Improvement
Components: Engine, TRACEMGR
Affects Versions: 4.0 Beta 1
Reporter: Rashid Abzalov
Adding the ability to trace (using fbtrace) server access to system tables. Now
the use of system tables are not visible when tracing.
This feature will allow to "see" for what the time is spent in some ambiguous
situations, such as, for example, CORE-5612.
Also, this opportunity can be used not only by those who understand the source
code of Firebird, but also by others. Now, without profiling skills, this
cannot be done without contacting the Firebird developers. But it seems to me
not rational to spend their time and professional skills on such issues,
because less experienced users would have coped with it.
On the other hand, the quality of the description of issues would be much
better, because they would be able to independently gather the necessary
information (with understanding of what is happening) before creating the
incident. And in some cases, they would not even begin to create an issue,
since would understand the problem or found the workaround yourself.
--
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
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
