mydumper does not force the dump query to use PRIMARY INDEX
Bug #1531350 reported by
Ovais Tariq
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL Data Dumper |
New
|
Wishlist
|
Max Bubenick | ||
Bug Description
In some cases MySQL can choose the wrong query plan so that it does not use the Primary Index when running the SELECT query that is used to dump the table. This can cause the dump query to take unnecessarily long time.
I would like to propose an option that would allow a user to specify that mydumper should always force the SELECT query to use the Primary Key if present or the first Unique key.
| Changed in mydumper: | |
| importance: | Undecided → Low |
| assignee: | nobody → Max Bubenick (max-bubenick) |
| importance: | Low → Wishlist |
To post a comment you must log in.
