myinsane segfault or kill the mysql server
Bug #914830 reported by
Frederic Descamps
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Data Recovery Tool for InnoDB |
Confirmed
|
Medium
|
Unassigned |
Bug Description
It seems that myinsane crashes when trying to validate dates on large tables:
./myinsane -u percona_root -pxxxxxx -d xxxx -t xxxx_stats -c 130790448
-s
Segmentation fault
select count(*) from xxxx_stats;
+-----------+
| count(*) |
+-----------+
| 128357598 |
+-----------+
1 row in set (6 min 56.13 sec)
this works:
./myinsane -u percona_root -pxxxxxxx -d xxxx -t xxxx_stats -c 130790448
This not it seems:
./myinsane -u percona_root -pxxxxxxx -d xxxx -t xxxx_stats -s
Killed
It seems the resultset it too heavy for this server ?
Changed in percona-data-recovery-tool-for-innodb: | |
status: | New → Confirmed |
Changed in percona-data-recovery-tool-for-innodb: | |
assignee: | nobody → Aleksandr Kuzminsky (akuzminsky) |
importance: | Undecided → Medium |
Changed in percona-data-recovery-tool-for-innodb: | |
assignee: | Aleksandr Kuzminsky (akuzminsky) → nobody |
To post a comment you must log in.
This change the way myinsanechecks the date ,this returns a smaller resultset.
Also this patch add a new parameter to my insabe (-r ) to define the difference between expected and actual number of rows in % when using -c