MySQL Forums :: Partitioning :: wrong output generate while using partitions


Advanced Search

Re: wrong output generate while using partitions
Posted by: Rick James ()
Date: December 16, 2014 04:28PM

Jon, when you ran it, what did the EXPLAIN say? What version were you running? For me, it did not say index merge / intersect.

This bug fix may be relevant:

----- 2014-09-25 5.7.5 Milestone 15 & 2014-03-27 5.6.17 -- Bugs Fixed -- Partitioning -----

When the index_merge_intersection flag (enabled by default) or the index_merge_union flag was enabled by the setting of the optimizer_switch ( http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_optimizer_switch ) system variable, queries returned incorrect results when executed against partitoned tables that used the MyISAM ( http://dev.mysql.com/doc/refman/5.7/en/myisam-storage-engine.html ) storage engine, as well as partitioned InnoDB ( http://dev.mysql.com/doc/refman/5.7/en/innodb-storage-engine.html ) tables that lacked a primary key. (Bug #18167648)

Shivam, always have an explicit PRIMARY KEY on InnoDB tables.
So do one of these:
* Add a PK
* Upgrade to 5.6.17 (or later)
* Turn off index_merge_intersection

Options: ReplyQuote


Subject Views Written By Posted
wrong output generate while using partitions 1884 Shivam Patel 12/13/2014 07:56AM
Re: wrong output generate while using partitions 905 Rick James 12/14/2014 10:33PM
Re: wrong output generate while using partitions 876 Shivam Patel 12/16/2014 01:24AM
Re: wrong output generate while using partitions 931 Jonathan Stephens 12/16/2014 02:32AM
Re: wrong output generate while using partitions 947 Shivam Patel 12/16/2014 04:00AM
Re: wrong output generate while using partitions 863 Rick James 12/16/2014 04:28PM
Re: wrong output generate while using partitions 976 Shivam Patel 12/17/2014 07:20AM
Re: wrong output generate while using partitions 987 Rick James 12/17/2014 11:27AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.