Subject RE: [ib-support] SELECT COUNT(*) ... - slow
Author Tobias Giesen
> And the reason it doesn't, is that there may be
> different numbers of rows for different concurrent
> transactions.

So what? It could maintain separate counters for each
transaction, as well as a main counter for the committed
rows. I'm sure it could.

However, this optimization feature doesn't seem to have
been considered worth it.