So, in case of * NOT Innodb * storage engine, say MyISAM, will this dump be
of any useful?
Best Regards,
Geetanjali Mehra
Senior Oracle and MySQL DBA Corporate Consultant and Database Security
Specialist
On Tue, Oct 7, 2014 at 11:55 AM, yoku ts. wrote:
> Hello,
>
> If you use any *NOT InnoDB*
Hello,
If you use any *NOT InnoDB* storage engine, you're right.
mysqldump with --single-transaction doesn't have any consistent as you say.
If you use InnoDB all databases and tables, your dumping process is
protected by transaction isolation level REPEATABLE-READ.
http://dev.mysql.com/doc/refm
It seems to me that once the read lock is acquired, only the binary log
coordinates are read. Soon after binary log coordinates are read, lock is
released. Is there anything else that happens here?
It means that after lock is released, dump is made while the read and write
activity is going on.
Hello Geetanjali,
On 9/23/2014 7:14 AM, geetanjali mehra wrote:
Can anybody please mention the internals that works when we use mysqldump
as follows:
*mysqldump --single-transaction --all-databases > backup_sunday_1_PM.sql*
MySQL manual says:
This backup operation acquires a global read lock
Any body have a working sample call to mysql_options() for this option can't
seem to get it to work.
Sent from my iPhone
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
