>> There is idea to add trace event for every point at PSQL module which >> was >> recognized by parser as start of some statement (the line numbers available >> at debug info\call stack). >> > > I think these ideas should not mix concepts of trace with debug and > profile. So for what it will be useful?
IMHO, at Trace API output level, it would be sufficient to get appropriate EXECUTE_STATEMENT_* or EXECUTE_PROCEDURE_* trace events with all the stuff like execution time, I/O stats ... for embedded calls in other PSQL code modules. The current trace output for procedure calls is kind of a black box for the Trace API end user. Just a thought. Regards, Thomas > Adriano > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
