Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
merge 5.7 P_S memory instrumentation and tables
perhaps we can get rid of MY_THREAD_SPECIFIC and deduce this from the P_S key?
Attachments
Issue Links
- duplicates
-
MDEV-16626 Performance schema lacks memory usage instrumentation
-
- Closed
-
-
MDEV-20499 Backport Performance Schema Memory Instrumentation from MySQL 5.7
-
- Closed
-
- is part of
-
MDEV-6114 merge new P_S instrumentation and tables from 5.7
-
- Closed
-
- relates to
-
MDEV-20455 memory leak in 10.4 series
-
- Closed
-
Activity
Link |
This issue duplicates |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.4 [ 22408 ] |
Support case ID | 27439 |
Link |
This issue relates to |
Link |
This issue duplicates |
Description | merge 5.7 P_S memory instrumentation and tables |
merge 5.7 P_S memory instrumentation and tables
perhaps we can get rid of MY_THREAD_SPECIFIC and deduce this from the P_S key? |
Component/s | Admin statements [ 11400 ] | |
Fix Version/s | 10.5.2 [ 24030 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 87744 ] | MariaDB v4 [ 133586 ] |
Component/s | Performance Schema [ 15627 ] |
Zendesk Related Tickets | 126951 151275 |