I did try to to set the lockTables to false in the XML configuration file, unfortunately this does not add appropriate parameter to the mysqldump command.
It also would be nice to have 'single-transaction' option available.
The text was updated successfully, but these errors were encountered:
That is very true and I already verified it in a dry run with phpbu --simulate.
However mysqldump by default has the lock-tables value set to TRUE, therefore running this command without lock-tables parameter will effectively run it like with lock-tables=true.
If I understand the mysqldump docs correctly, by default --lock-tables is deactivated.
Some options like --opt enable --lock-tables but by default it is not active.
To actively deactivate it one should use --skip-lock-tables
For each dumped database, lock all tables to be dumped before dumping them.
The tables are locked with READ LOCAL to permit concurrent inserts in the case
of MyISAM tables. For transactional tables such as InnoDB, --single-transaction
is a much better option than --lock-tables because it does not need to lock the
tables at all.
Because --lock-tables locks tables for each database separately,
this option does not guarantee that the tables in the dump file are
logically consistent between databases. Tables in different databases
may be dumped in completely different states.
Some options, such as --opt, automatically enable --lock-tables.
If you want to override this, use --skip-lock-tables at the end of the option list.