MySQL Bugs: #38571: need better docs on how temporary tables are replicated

Bug #38571	need better docs on how temporary tables are replicated
Submitted:	5 Aug 2008 13:06	Modified:	7 Aug 2008 16:46
Reporter:	Axel Schwenke	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
The documentation is a bit sparse when it comes to replication of temporary tables. One unexpected feature is, that temporary tables are replicated even when there is no matching replicate-[wild-]do-table option.

Of course SBR must replicate all temporary tables in order to be able to handle situations like this:

CREATE TEMPORARY TABLE foo.bar;
-- fill data into foo.bar
INSERT INTO replicated_table SELECT ... FROM foo.bar;

How to repeat:
n/a

Suggested fix:
Extend the documentation. Add some words for the following facts:

- by default SBR replicates all temporary tables, regardless if they match a replicate-[wild-]do option on the slave or not

- it is however possible to use a replicate-[wild]ignore option to suppress the replication of temporary tables

- the following is good praxis: temporary tables that are created for selects only, should get a descriptive name (prefix) and a matching replicate-wild-ignore-table option on the slave. This will also take some load from the slave.

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.