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
-
This would be good for compatibility with MySQL but also because "memory issues do occur" and in the past it has been very hard to determine where the memory was going and thus find the cause.