[MDEV-25687] trx_active_transactions is inconsistent and a potential performance hog; remove it Created: 2021-05-17 Updated: 2021-05-17 Resolved: 2021-05-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.0, 10.1, 10.2, 10.3, 10.4, 10.5, 10.6 |
| Fix Version/s: | 10.6.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | corruption, performance | ||
| Issue Links: |
|
||||||||||||
| Description |
|
The counter MONITOR_TRX_ACTIVE is not being updated consistently; see MySQL Bug #73114. Furthermore, the count aims to include non-locking read-only transactions, which are otherwise mostly invisible to other threads, for performance reasons. The more interesting transactions can be found by reading information_schema.innodb_trx. If it later turns out that a reliable count of active transactions is needed, it can be implemented via a different interface later. |