MySQL Bugs: #26525: Add --skip-thread option to mysqlbinlog

Bug #26525	Add --skip-thread option to mysqlbinlog
Submitted:	21 Feb 2007 13:30
Reporter:	Mark Leith	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S4 (Feature request)
Version:		OS:
Assigned to:		CPU Architecture:	Any
Tags:	mysqlbinlog

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
With mysqlbinlog it is currently not possible to ignore all events for a specific thread ID. 

This would be helpful in certain recovery operations where you want to skip all events generated by a specific thread (such as a bad DROP TABLE, a bad recovery attempt of a mysqldump file, some script that was run wrongly). 

Right now we can only go by --start-datetime etc. - however, if a thread executes many statements, there is the possibility that there could be many events that are "interleaved" with other threads events - making the recovery long and arduous as you figure out the many start/stop times to skip over each event.

How to repeat:
Nothing to repeat currently.