Nasty Regression Bug: SELECT COUNT(DISTINCT) crashes InnoDB when WHERE operand is in Primary Key or Unique Index

In 5.5, a crashing, regression bug exists if you use SELECT COUNT(DISTINCT) *and* one of the WHERE operands is in the Primary Key (or just a unique index).

** Update: This bug may be fixed in 5.5.18. At least initial my initial test (the test case provided below) did not crash in 5.5.18. The MySQL Dev Team has not confirmed if this has been fixed or not, nor is there any mention of a fix in the 5.5.18 changelogs, so proceed with caution.

Note this bug does *not* affect any version of MariaDB – 5.1, 5.2, or 5.3. ** (12/5/2011)

This simple crash (if only one row is in the table) will crash mysqld.

Of course I’ve filed a bug report, but that has been nearly 3 months and no updates yet.

Here is the bug I filed (which you won’t be able to view):

Really, the only thing that happened to my bug report was that it was designated a duplicate of another bug (which we also cannot view):

Based on the id, and the submitted dates of bugs 61100 and 61102, this initial bug (61101) was filed on May 9, 2011. So, in fact, this bug has been present for over 5 months, and not one breath of an update to the public!

Therefore, I felt it necessary to warn others about this bug, (or possibly you’ll run across this if you’re searching on SELECT COUNT(DISTINCT) in the future).

All I can say is please watch out for it!

It is extremely easy to reproduce:

CREATE TABLE t (a int(1), b int(1), PRIMARY KEY (a,b)) ENGINE=InnoDB;

–> crash <--

For those interested, this was filed against 5.5.14. However, with each new release, I've continued testing, and this bug is present in 5.5.15, 5.5.16, and thus far in 5.5.17 (built from the latest bzr tree).

Hopefully we don't go too many more months before this is finally fixed.

And for reference (and those searching on the stack trace / error log messages), here is my full error log snippet from 5.5.16:

111017 10:54:47 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: ‘5.5.16’  socket: ”  port: 3308  MySQL Community Server (GPL)
 len 128; hex f8aec9037d803805f017fc03189ddc030000000…
111017 10:55:12  InnoDB: Assertion failure in thread 5000 in file btr0pcur.c line 236
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
111017 10:55:12 – mysqld got exception 0xc0000005 ;
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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58325 K
bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x3c98428
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…
00CE92EC    mysqld.exe!btr_pcur_restore_position_func()[btr0pcur.c:236]
00CA62FB    mysqld.exe!sel_restore_position_for_mysql()[row0sel.c:3081]
00CA6CEA    mysqld.exe!row_search_for_mysql()[row0sel.c:3820]
00C5FE20    mysqld.exe!ha_innobase::general_fetch()[]
00C5FEDD    mysqld.exe!ha_innobase::index_next()[]
00C20DDA    mysqld.exe!index_next_different()[]
00C249BC    mysqld.exe!QUICK_GROUP_MIN_MAX_SELECT::next_prefix()[]
00C26BE7    mysqld.exe!QUICK_GROUP_MIN_MAX_SELECT::get_next()[]
00B68D01    mysqld.exe!rr_quick()[]
00BC1B9A    mysqld.exe!sub_select()[]
00BD10A7    mysqld.exe!do_select()[]
00BD37BD    mysqld.exe!JOIN::exec()[]
00BD3A29    mysqld.exe!mysql_select()[]
00BD3D4B    mysqld.exe!handle_select()[]
00ACD76E    mysqld.exe!execute_sqlcom_select()[]
00ACF816    mysqld.exe!mysql_execute_command()[]
00AD2D1F    mysqld.exe!mysql_parse()[]
00AD3848    mysqld.exe!dispatch_command()[]
00AD43BB    mysqld.exe!do_command()[]
00AF2DB6    mysqld.exe!do_handle_one_connection()[]
00AF2F44    mysqld.exe!handle_one_connection()[]
00C33DE4    mysqld.exe!pthread_start()[my_winthread.c:61]
00D9C6F3    mysqld.exe!_callthreadstartex()[threadex.c:348]
00D9C79B    mysqld.exe!_threadstartex()[threadex.c:326]
765F3823    kernel32.dll!BaseThreadInitThunk()
77CAA9BD    ntdll.dll!LdrInitializeThunk()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Connection ID (thread ID): 1

The manual page at contains
information that should help you find out what is causing the crash.
InnoDB: Thread 5980 stopped in file os0sync.c line 781
InnoDB: Thread 6820 stopped in file os0sync.c line 474
InnoDB: Thread 7532 stopped in file os0sync.c line 474

10 thoughts on “Nasty Regression Bug: SELECT COUNT(DISTINCT) crashes InnoDB when WHERE operand is in Primary Key or Unique Index”

  1. Rofl!
    Thx for letting us know.
    Crashes with 5.6.2 too.
    Works with MariaDB 5.2.7 and 5.3.1. (Ok thats logic)

  2. I can confirm that your example crashed our Percona 5.5.16 test machine.
    However I did a cross check on another database/table at the same machine containing a similar layout (and some extra columns) and it did not crash at all.

    I’ve also altered your example with another column:
    And now your query doesn’t crash InnoDB anymore.
    Also when I created a new table with the column types of a and b as a varchar(1) it did not crash.

    Looks like the problem may be isolated to a table containing only two integer columns and a primary key and/or unique set to them. Still there are lots of databases containing these type of tables…

  3. Confirmed Art van Scheppingen’s test (and suggestion as to the problem) on MySQL Community Edition 5.5.12 by adding a VARCHAR column. Good catches all around.

  4. Er.. corrected typo in email for registration.

    Confirmed Art van Scheppingen’s test (and suggestion as to the problem) on MySQL Community Edition 5.5.12 by adding a VARCHAR column.

    Good catches all around.

  5. Wow. Can also verify with more columns. From a production schema in a test environment, names redacted.

    Server version: 5.5.12 MySQL Community Server (GPL)
    Server version: 5.5.15-log MySQL Community Server (GPL)

    DROP TABLE IF EXISTS i_x_metrics;
    CREATE TABLE i_x_metrics (
    y_id int(10) unsigned NOT NULL,
    x_id int(10) unsigned NOT NULL,
    h_id int(10) unsigned NOT NULL,
    g_id int(10) unsigned NOT NULL,
    i_id int(10) unsigned NOT NULL,
    count_1 int(10) unsigned NOT NULL,
    count_2 int(10) unsigned NOT NULL,
    count_3 int(10) unsigned NOT NULL,
    count_4 int(10) unsigned NOT NULL,
    count_5 int(10) unsigned NOT NULL,
    count_6 int(10) unsigned NOT NULL,
    PRIMARY KEY (i_id,x_id),
    KEY idx_h_id (h_id),
    KEY idx_g_id (g_id),
    KEY idx_y_id (y_id),
    KEY idx_x_id (x_id)
    ) ENGINE=InnoDB;

    INSERT INTO i_x_metrics VALUES(1,1,1,1,1,1,1,1,1,1,1);
    SELECT COUNT(DISTINCT i_id) FROM i_x_metrics WHERE x_id = 1;

    ERROR 2013 (HY000): Lost connection to MySQL server during query

  6. If you CREATE the table using a UNIQUE KEY instead of a PRIMARY KEY, then that is a valid work-around.

    However, if you ALTER the existing table to use a UNIQUE KEY instead of the PRIMARY KEY, then it will still crash.

  7. Just tested this on 5.5.18, and it’s not crashing.

    Perhaps it’s been fixed .. need to test more, but wanted to post that.

    The 5.5.18 changelogs don’t appear to list a specific bug fix that would seem to cover this.

    I’m trying to get confirmation via the bug report I posted.

  8. Hi ypercube,

    I don’t think this is the same bug. This bug is more about the crashing, and requires a SELECT COUNT (DISTINCT) specifically, plus the WHERE operand is in the Primary Key or Unique index.

    Your bug/issue does not have the DISTINCT, it is not crashing, and the index on the datetime column is not a primary key nor unique. However, it is a bit strange off the cuff, so I did some searching though, and ran across this bug, which seems more likely to be involved/related:

    Actually, it is designated as “not a bug”, but it shows/describes how you can run into strange behavior when you have dates/datetimes with ‘0000-00-00′ and using IS NULL and IS NOT NULL.

    I wonder if you have any of these ‘0000-00-00′ rows which could be affecting the counts?

    Note the Dev who comments in the bug report mentions this page too:

    If that is not it, I’d certainly recommend upgrading and trying this on the latest 5.5, which is 5.5.21 (as of 2/22/2012), since it has been 9 months (and 9 releases) since 5.5.12 was released.

    Note you should be able to dump the table (and data) and import it into another test instance, just to test it out. That way you do not affect a production machine, and you can have a test instance set up in minutes.

    Then, should that that not make a difference still, you’d be in a position to test some other items, such as perhaps convert the table to MyISAM to see if the issue is a global one, or just specific to InnoDB.

    Or, I noticed the index on ‘estimated_date’ was:

    KEY `estimated_date_index` (`estimated_date`) USING BTREE

    Note the “USING BTREE”. Perhaps try it without the USING BTREE and see if you still see the same behavior. (Or remove the index altogether just to test .. it will all help narrow down the issue).

    Hope this helps.

Comments are closed.