MySQL Bugs: #54884: docs for replicate-ignore-db, replicate-ignore-table are ambiguous

Bug #54884	docs for replicate-ignore-db, replicate-ignore-table are ambiguous
Submitted:	29 Jun 2010 1:08	Modified:	20 Aug 2010 13:26
Reporter:	Mark Callaghan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	ALL	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	IGNORE, replication

Description:
The docs in these sections are ambiguous:

http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html#option_mysqld_replic...

http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html#option_mysqld_replic...

The docs for the --replicate-do-* options have similar problems

How to repeat:
>>>
 Tells the slave thread to not replicate any statement that updates the specified table, even if any other tables might be updated by the same statement. To specify more than one table to ignore, use this option multiple times, once for each table. This works for cross-database updates, in contrast to --replicate-ignore-db. See Section 16.2.3, “How Servers Evaluate Replication Filtering Rules”.

This option affects only statements that apply to tables. It does not affect statements that apply only to other database objects, such as stored routines. To filter statements operating on stored routines, use one or more of the --replicate-*-db options. 
>>>

What is "the slave thread"? MySQL has two slave threads -- one for IO, one for SQL.

What does it mean to "not replicate"?
* the IO thread does not record the event
* the SQL thread does not replay the event

Suggested fix:
update the docs

Set target and priority.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.