28.09.2020 20:44, Adriano dos Santos Fernandes wrote:
I have thought on that possibility since the start and the conflict
points I see are:
- Name of RDB$PROFILE_STATS - perhaps RDB$PROFILE_PSQL?
Maybe we may leave it as is. And add RDB$PROFILE_CURSOR_STATS.
The question is how they should be linked. Some artificial unique cursor
ID added to RDB$PROFILE_STATS for lines containing queries? Or should
RDB$PROFILE_CURSOR_STATS duplicate LINE/COLUMN as a reference? What if
the statement has multiple sub-queries?
BTW, execution time is good but I believe all other statistics
(page-level, record-level, memory) should also be collected/reported
while profiling. Mostly this is about cursors, but not only (singleton
INSERTs for example).
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
