slow dumping of mysql in production about backup HOT 8 CLOSED

You can inform this option in your configuration file using 'additional_options' like this:

adapter :mysql do
  user        'user'
  password    'password'
  database    'database'
  skip_tables ['table1', 'table2', 'table3']
  options do
    host    '123.45.678.90'
    port    '80'
    socket  '/tmp/socket.sock'
  end
  additional_options '--single-transaction'
end

from backup.

This isn't really an issue, but we could perhaps just implement that this is default behavior. What are the pros en cons of using --single-transaction?

from backup.

As far as I know you almost always want to use
additional_options '--single-transaction --quick'
if your database supports transactions (mysql does)

from backup.

Thanks for pointing that out, I will mark this as a consideration. Might be a good idea set these options as defaults.

from backup.

Mysql doesn't support transactions, some storage engine does, like InnoDB. I don't think this option should be enabled by default, because other people uses other storage engines.

from backup.

Good point, I did not know that. In that case it's not wise to set it as default since it will literally break MySQL adapter for some users.

I guess the commented out template in the backup configuration file will be enough to point out the option IS available but needs to be activated: additional_options '--single-transaction'.

We could additionally add this that line: --quick so it would make: --single-transaction --quick.

from backup.

I will add the --single-transaction --quick to the generated template, but leave it commented out. Maybe add a comment that tell it to uncomment this line if the database is large so that it doesn't lock tables and such, but that it isn't supported for all storage engines.

from backup.

That sounds like a great idea. Thanks.

from backup.