Francisco Rodrigo Cortinas Maseda wrote:
Hi,
I have experienced similar problems to the one you have; the problem you have
is that the time gap between the failure and now is so big that you cannot
resume replication, because of the big data portion you have to replicate.
Well, that was yesterday - so I guess I could.
I see the binlog ids where replication stopped and resumed. They match
every time. How would I find out that replication resumed at a wrong
position?
Regards
Dominik
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
