Percona Server 5.1.58 crashes on a specific query
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Laurynas Biveinis | ||
5.1 |
Fix Released
|
Undecided
|
Laurynas Biveinis |
Bug Description
FYI, this bug also affects MySQL vanilla release version 5.1.58. However this bug does not seem to affect Percona Server 5.5.15
=== Version info
mysql [localhost] {msandbox} (crash_test) > select version();
+---------------+
| version() |
+---------------+
| 5.1.58rel12.9 |
+---------------+
=== Table structure that produces a crash
CREATE TABLE `crash_tbl` (
`id` varchar(32) NOT NULL,
`customer_name` varchar(50) NOT NULL COMMENT 'account name',
`tenant_id` varchar(32) NOT NULL COMMENT 'Save Tenant id',
`deleted` bit(1) DEFAULT b'0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
=== Query that produces the crash
select id from crash_tbl
where tenant_id='10513' and deleted=0
and
(
customer_
or
customer_
);
=== Relevant text from error log
111217 9:56:15 - mysqld got signal 11 ;
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.
key_buffer_
read_buffer_
max_used_
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x586a7b0
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 = 0x41b520e8 thread_stack 0x40000
/usr/local/
/usr/local/
/lib64/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5892a00): select id from crash_tbl where tenant_id='10513' and deleted=0 and ( customer_
Connection ID (thread ID): 1
Status: NOT_KILLED
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 51 lines (+16/-2)3 files modifiedPercona-Server/mysql-test/r/bug63793.result (+5/-0)
Percona-Server/mysql-test/t/bug63793.test (+9/-0)
Percona-Server/sql/sql_select.cc (+2/-2)
Changed in percona-server: | |
assignee: | nobody → Laurynas Biveinis (laurynas-biveinis) |
Changed in percona-server: | |
status: | New → In Progress |
milestone: | none → 5.1.61-13.2 |
Changed in percona-server: | |
status: | In Progress → Fix Committed |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
Ovais,
Does it reproduce on upstream MySQL 5.1.58?