Dangerous behaviour with mysqlDump
it seems there is a strange behaviour of mysqldump when encoutring crashed(corrumpted) table , he may hang and create same temporarily or buffer file with infinite loop or something like that for my case it is reaching more than 300G for a db that contain less than 80M ??
so the question is : what should be the result of :
/usr/bin/mysqldump --routines -c -Q -q dbName
if dbName contain crashed table ?
Subject
Written By
Posted
Dangerous behaviour with mysqlDump
March 28, 2013 09:39AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.