Bug #83626 Collect per column usage data in performance_schema

• Submitted: 1 Nov 2016 7:30
• Modified: 3 Nov 2016 6:58
• Reporter: Daniël van Eeden (OCA)
• Status: Verified
• Category: MySQL Server: Performance Schema
• Severity: S4 (Feature request)
• Version: 5.7.16
• OS: Any
• CPU Architecture: Any

[1 Nov 2016 7:30] Daniël van Eeden

Description:
It would be useful to have data for a column about if that column gets any reads and/or writes.

We do have query text, but that might give false positives.
The optimizer should have the real (non aliased) column names.

This probably has a high overhead, but enabling it on a per column basis would be fine.

How to repeat:
Try to get data about the usage of one particular column, e.g. to make sure it's not used before dropping (or renaming) it.

Suggested fix:
Add per column instrumentation to performance_schema.

[3 Nov 2016 6:58] MySQL Verification Team

Hello Daniël,

Thank you for the feature request!

Thanks,
Umesh