Bug #80342 | session_track_gtids is not optimal | ||
---|---|---|---|
Submitted: | 11 Feb 2016 15:04 | Modified: | 11 Feb 2016 15:42 |
Reporter: | Mikiya Okuno | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[11 Feb 2016 15:04]
Mikiya Okuno
[11 Feb 2016 15:05]
MySQL Verification Team
Ugly ugly test program. Modify credentials according to your environment.
Attachment: gtid-test.c (text/x-csrc), 3.84 KiB.
[11 Feb 2016 15:07]
MySQL Verification Team
You need following server options to run this program: log_bin=mysql-bin server_id=1 gtid_mode=on enforce_gtid_consistency=on session_track_gtids=OWN_GTID
[11 Feb 2016 15:09]
MySQL Verification Team
The test program can return GTID in the OK packet, actually. Because it issues a "SET GTID_NEXT" command beforehand. IMHO, "SET GTID_NEXT" should be unnecessary.
[11 Feb 2016 15:29]
MySQL Verification Team
Test program without SET GTID_NEXT
Attachment: gtid-test-rev2.c (text/x-csrc), 2.48 KiB.
[11 Feb 2016 15:42]
MySQL Verification Team
I'm sorry. I made a mistake in sequence of calling API functions. This is not a bug. Please close.