[MDEV-6726] CONNECTION_ATTRS not stored in performance schema Created: 2014-09-10 Updated: 2014-10-09 Due: 2014-09-30 Resolved: 2014-10-09 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 10.0.12 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Georg Richter | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | upstream | ||
| Environment: |
Linux x64 |
||
| Description |
|
Both mysql_client_test (from MySQL Server package) and mariadb-native-client test suite suite fail, since connection attributes are not stored in performance schema. Test:
|
| Comments |
| Comment by Elena Stepanova [ 2014-09-23 ] | |
|
Are you running the server with --performance-schema? | |
| Comment by Georg Richter [ 2014-09-23 ] | |
|
Hi Elena, i wasn't aware that performance-schema was disabled by default.
will fail. | |
| Comment by Elena Stepanova [ 2014-09-23 ] | |
|
According to the documentation (http://dev.mysql.com/doc/internals/en/capability-flags.html), the flag only means that the server allows connection attributes in Protocol::HandshakeResponse41. It still does, whether performance schema is enabled or not, so why should this check fail? | |
| Comment by Elena Stepanova [ 2014-09-24 ] | |
|
In any case, it's an upstream problem. It would be particularly unfortunate if our server or clients became incompatible with the upstream on this level. georg | |
| Comment by Sergei Golubchik [ 2014-10-09 ] | |
|
I believe it is not a bug. The server supports connection attributes, it knows how to parse the packet with them, that's why the capability bit is set. Whether the server will store them or throw away is a separate issue. Currently, the server stores them in the performance schema, that's why if performance schema is disabled — connection attributes are not stored. |