Subject Re: how to retrieve the IDX_READS and the SEQ_READS of a statement or a transaction
Author emb_blaster
> > so taking again just after the isc_info_read_idx_count can not be
> > accurate :(
> If you use ClassicServer or SuperClassic it will be accurate.
> Another possibility is to use Trace API (in Firebird 2.5 of course).
> Regards,
> Vlad

Just to clarify, even on CS or SC, diferents statments running in same time will be accurate (mean the return of isc_info_read_idx_count) because it will use diferent transactions for each, right? Or even if i could use the same transaction to booth multithread queries isc_info_read_idx_count will return a correct value?