Re: Alt index search on partitioned table
Posted by:
Rick James
Date: February 24, 2014 05:49PM
If you have a separate column for the partition number, you could get it to do "pruning".
True, the current version of MySQL fails to touch all the partitions in parallel. That feature may be available in a year or so.
SHA1 (and any other digest) is a terribly way to index any huge table. It is very random, so the caching is virtually useless unless you have some rows that are frequently used.
Don't PARTITION unless you have over a million rows in the table.
EXPLAIN PARTITION SELECT ... to see if it does the pruning.
An AUTO_INCREMENT need not be declared UNIQUE or PRIMARY.
Why do you need to auto_inc if you have a SHA1?
Provide
SHOW CREATE TABLE
SELECT ...
so we can discuss the performance issues further.
Subject
Views
Written By
Posted
2873
February 20, 2014 02:46PM
Re: Alt index search on partitioned table
1555
February 24, 2014 05:49PM
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.