Hi all
As for my deep opinion gstat must not modify database
as that is pure read-only utility. Unfortunately this is not so
if OAT - OIT > sweep_interval and user want something more
than just header page statistics. In that case gstat start its own
transaction and triggers sweep and statistics can be gathered
much longer time than expected and next run will return another
info.
To fix it we have two alternatives :
1. check ATT_gstat_attachment in TRA_start before
start sweep
2. add isc_dpb_no_garbage_collect to gstat's dpb
and check for ATT_no_cleanup in TRA_start
I prefer second approach as more general.
Opinions ?
Regards,
Vlad
|
