[MDEV-16431] merge 5.7 P_S memory instrumentation and tables Created: 2018-06-08  Updated: 2023-02-03  Resolved: 2020-03-11

Status: Closed
Project: MariaDB Server
Component/s: Admin statements, Performance Schema
Fix Version/s: 10.5.2

Type: Task Priority: Major
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Fixed Votes: 6
Labels: None

Issue Links:
Duplicate
duplicates MDEV-16626 Performance schema lacks memory usage... Closed
duplicates MDEV-20499 Backport Performance Schema Memory In... Closed
PartOf
is part of MDEV-6114 merge new P_S instrumentation and tab... Closed
Relates
relates to MDEV-20455 memory leak in 10.4 series Closed

 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?



 Comments   
Comment by Simon Mudd [ 2018-06-27 ]

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.

Comment by Simon Mudd [ 2019-04-05 ]

Bumped into a memory issue in 10.3.13 where this would have been useful for tracing the issue.

Comment by Muhammad Omair [ 2021-02-26 ]

@Simon Mudd Can you specify what kind of memory issue you had experienced with 10.3.13? Were you able to fix it by a configuration change or did you do a minor/major upgrade to resolve it?

Generated at Thu Feb 08 08:28:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.