Re: mysql dump global read lock
Lisa Smith <[email protected]>
| Newsgroups | gmane.comp.db.mysql.general |
|---|---|
| Message-ID | <CAOEVzykXPEw7bV2yM7V+Yemz5HgRmOVLR6o9rrkkiK0nzfwkUw@mail.gmail.com> |
Artem, You have --add-locks listed which will run LOCK TABLES prior to each table dump. --single-transaction is for InnoDB tables and ensures that they are copied in a consistent state. I hope this helps! On Thu, Dec 17, 2015 at 4:24 PM, Artem Kuchin <[email protected]> wrote: > Hello! > > Hereis my mysqldump command line > > mysqldump -u root --events --complete-insert --skip-opt > --single-transaction --add-drop-table --add-locks --create-options > --disable-keys -- > extended-insert --quick --set-charset --routines --triggers --hex-blob > DB_NAME > > But i see tons of Waiting for global read lock > in show processlist for many tables in many different databases for all > modification queries and locks > > Why? As i understood --skip-opt --single-transaction must disable global > read lock > > > mysql version > Server version: 5.6.27-log Source distribution > > Artem > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql > >