We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Piwik default table engine is InnoDB since Piwik 2.1.
In that case, mysqldump documentation recommends to use --single-transaction option instead of --lock-tables.
This avoids LOCKS conflicts with piwik application and has much better performances.
As --lock-tables is enabled by default (due to --opt shortcut option), you have to explicitly disable it:
mysqldump --skip-lock-tables --single-transaction ...
The text was updated successfully, but these errors were encountered:
Nice catch :) Do you want to PR? :P
(You must have a big setup to spot this? Or just reading the doc?)
Sorry, something went wrong.
I experienced this issue with an other application, and the performance impact is real when accessing to the database in write mode during the backup.
I don't know how it affects piwik, nor how piwik manages the DB pool, but it is a no-cost optimization, so enjoy! ;-)
Thanks @stefancrain
No branches or pull requests
Piwik default table engine is InnoDB since Piwik 2.1.
In that case, mysqldump documentation recommends to use --single-transaction option instead of --lock-tables.
This avoids LOCKS conflicts with piwik application and has much better performances.
As --lock-tables is enabled by default (due to --opt shortcut option), you have to explicitly disable it:
The text was updated successfully, but these errors were encountered: