**Reported in Launchpad by Cofyc last update 28-05-2013 06:41:28

I have a big table, around 15,000,000 rows.

When i query some special rows from table, like this one:

SELECT * FROM `post` WHERE postId = 8449114;

mysql crashes with following error:

121025 17:40:02 InnoDB: Assertion failure in thread 140112839591680 in file row/row0sel.c line 4563
InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOMMITTED
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:40:02 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=1048576
read_buffer_size=1048576
max_used_connections=2
max_threads=1024
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2109544 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

=====> backtrace

Thread pointer: 0x21bab180
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f6e90083e98 thread_stack 0x40000
/usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x35)[0x8a8aa5]
/usr/local/mysql/libexec/mysqld(handle_fatal_signal+0x378)[0x6adfb8]
/lib64/libpthread.so.0(+0x10310)[0x7f73d85a6310]
/lib64/libc.so.6(gsignal+0x35)[0x7f73d756a8e5]
/lib64/libc.so.6(abort+0x186)[0x7f73d756bd66]
/usr/local/mysql/libexec/mysqld[0x7aa0f1]
/usr/local/mysql/libexec/mysqld[0x743371]
/usr/local/mysql/libexec/mysqld(_ZN7handler15read_range_nextEv+0x59)[0x6a0419]
/usr/local/mysql/libexec/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_range+0x33)[0x69fb23]
/usr/local/mysql/libexec/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x167)[0x68cc37]
/usr/local/mysql/libexec/mysqld[0x69bd43]
/usr/local/mysql/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x5a)[0x61e37a]
/usr/local/mysql/libexec/mysqld[0x62f18a]
/usr/local/mysql/libexec/mysqld(_ZN4JOIN4execEv+0x913)[0x63aab3]
/usr/local/mysql/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x199)[0x63c679]
/usr/local/mysql/libexec/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x1c5)[0x63cfc5]
/usr/local/mysql/libexec/mysqld[0x5c7d01]
/usr/local/mysql/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x3b6)[0x5cab36]
/usr/local/mysql/libexec/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x51b)[0x5d0dab]
/usr/local/mysql/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xa11)[0x5d17c1]
/usr/local/mysql/libexec/mysqld(_Z10do_commandP3THD+0x128)[0x5d2448]
/usr/local/mysql/libexec/mysqld(handle_one_connection+0x9cd)[0x5c43dd]
/lib64/libpthread.so.0(+0x7c6c)[0x7f73d859dc6c]
/lib64/libc.so.6(clone+0x6d)[0x7f73d7609bcd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (21bbc320): SELECT * FROM `post` WHERE postId = 8449114;
Connection ID (thread ID): 1
Status: NOT_KILLED

====> Summary

First I can reproduce this error on 5.1.58 version, when I found a related bug http://bugs.mysql.com/bug.php?id=62037, and upgraded to lastest Percona-Server-5.1.65-rel14.0-475.Linux.x86_64 version, but I still got this error.

====> Questions

Is it a mysql bug? Or data in my table is corrupted?

How can fix this?