[Phpmyadmin-devel] Innodb and row exact count

Marc Delisle marc at infomarc.info
Wed Jul 24 22:09:34 CEST 2013

Le 2013-06-12 17:04, Marc Delisle a écrit :
> Le 2013-06-12 03:23, Michal Čihař a écrit :
>> Hi
>> Dne Tue, 11 Jun 2013 13:20:44 -0400
>> Marc Delisle <marc at infomarc.info> napsal(a):
>>> I don't find a winning solution so I'm seeking for advice. In this bug
>>> report [0], we see that it's annoying to have incorrect page navigation
>>> (page selector and arrows) for InnoDB.
>>> However, when I apply my proposed patch (which forces an exact count in
>>> sql.php), I see delays for larger InnoDB tables.
>>> For example, on MySQL 5.5.31, the first time I browse a table having one
>>> million rows, I wait for 9 seconds. I tried with 0.5 million and it was
>>> about 5 seconds. A few minutes afterwards, even after closing the
>>> browser, my big table starts to display in two seconds.
>>> I tend to find these delays acceptable and I propose to apply my patch.
>> I agree this is acceptable and agree with the patch for 4.0.4.
>> For 4.1 I'd go even further - drop MaxExactCount and use only not exact
>> counts on overview pages and count properly when browsing.
> Thanks, I'll have a look at this suggestion for 4.1.

Hmmm, I think we have a problem with exact counting, see

It's true that 750 M rows is a lot of rows...

Marc Delisle

More information about the Developers mailing list