Jesse wrote:
What is the event at that position in the binlog? Use the mysqlbinlog
tool to see, or on the master you can run SHOW BINLOG EVENTS (check
the manual for the full syntax).
If I'm reading this right (and I'm probably not), the log goes from
position 98 to position 557 Position 98 has a DELETE FROM query on the
mysql.db table. Position 557 has a FLUSH PRIVILEGES command.
The position doesn't make any sense to me.
The position is a byte offset. Here's a bogus sample I just cooked up:
# at 13634
#071001 14:07:40 server id 3 end_log_pos 13710 Query
thread_id=6 exec_time=0 error_code=0
use test/*!*/;
SET TIMESTAMP=1191262060/*!*/;
drop table t1/*!*/;
# at ....
The # at <num> is the position of the event. The timestamp, server id,
etc follow. The event shown goes from 13634 to 13710 and there's a lot
of timestamp and other mumbo-jumbo in most binlog events.
Hopefully that's enough info for you to decide whether you read it
right. But it looks like your slave had some issue with that. Do you
have a lot of privileges? One of the Google engineers told me he's
sometimes seen FLUSH PRIVILEGES break replication with a lot of privileges.
Whoever was doing that query should have been using GRANT and REVOKE
instead -- or DROP USER.
Baron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
