enterprise-support team mailing list archive

Thread
Date

[Bug 1531350] [NEW] mydumper does not force the dump query to use PRIMARY INDEX

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Ovais Tariq <1531350@xxxxxxxxxxxxxxxxxx>
Date: Wed, 06 Jan 2016 00:54:20 -0000
Reply-to: Bug 1531350 <1531350@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

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.

** Affects: mydumper
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1531350

Title:
  mydumper does not force the dump query to use PRIMARY INDEX

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1531350/+subscriptions