constraints_parser is slooow when the table is big, i.e. there is a huge number of pages

Bug #624458 reported by Aleksandr Kuzminsky on 2010-08-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Data Recovery Tool for InnoDB
Aleksandr Kuzminsky

Bug Description

At the moment constraints_parser can process one InnoDB page.
If the table is big, the number of the pages is huge.
Thus, a wrapped script spends most time on forking contraints_parser processes.
The solution would be if the parser could process all pages from the given directory.

Changed in percona-innodb-recovery-tool:
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
importance: Undecided → Wishlist
Changed in percona-data-recovery-tool-for-innodb:
status: New → Confirmed

it was fixed ages ago

Changed in percona-data-recovery-tool-for-innodb:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers