Bug #68181 Release notes for 5.6.11 reference wrong bug number

Submitted:	25 Jan 2013 17:21	Modified:	29 Jan 2013 14:55
Reporter:	Valeriy Kravchuk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.6.11	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
Manual page http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-11.html says:

"Replication: In order to provision or to restore a server using GTIDs, it is possible to set gtid_purged to a given GTID set listing the transactions that were imported. This operation requires that the global gtid_executed and gtid_purged server system variables are empty. (This is done in order to avoid the possibility of overriding server-generated GTIDs.)

The error message GTID_PURGED can only be set when GTID_EXECUTED is empty that was raised when this requirement was not met could be confusing or misleading because it did not specify the scope of the affected variables. To prevent this from happening, error messages that refer to variables relating to GTIDs now specify the scope of any such variables when they do so. (Bug #16084426, Bug #68083)" 

Bug #68083 above is incorrect. It is bug #68038 actually.

How to repeat:
Check bug #68083 and compare to bug #68038 and manual page content.

Suggested fix:
s/68083/68038/

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.

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.