| Bug #87559 | events_transactions_current:gtrid is not properly displayed | ||
|---|---|---|---|
| Submitted: | 28 Aug 2017 9:08 | Modified: | 13 Oct 2017 16:27 |
| Reporter: | Venkatesh Duggirala | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 8.0.3 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[13 Oct 2017 16:27]
Paul DuBois
Posted by developer: Fixed in 8.0.4, 9.0.0. Values in the XID_GTRID column of the Performance Schema events_transactions_current table were displayed incorrectly for XA transactions.
Description: gtrid value in events_transactions_current is correctly displayed for XA transaction before commit 655e0c9b8541df6c6324c6f89847e1b8cf6ddc52 Author: Erik Froseth <erik.froseth@oracle.com> Date: Fri Jun 30 08:35:40 2017 +0200 WL#9223 Using histogram statistics in the optimizer But after this push, it is displaying in different format. How to repeat: Steps to reproduce the issue: 1) connection 1 >> create table t1 (a int) engine=innodb; >> xa start 'test1'; >> insert t1 values (10); >> xa end 'test1'; >> xa prepare 'test1'; 2) connection 2 >> select XID_GTRID from performance_schema.events_transactions_current; On a patch before WL#9223 pushed: will display 'test1'. On a patch after WL#9223 pushed : will display '0x4D7953514C58696401000000000000001800000000000000' Suggested fix: GTRID should be the same as what user provided. In the above example, it should display 'test1'