Details
-
Epic
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
InnoDB trx_sys improvements
Description
This issue is created for tracking a few remaining/discovered issues after the big InnoDB trx_sys refactoring.
The following don't yet have corresponding jira task:
- decouple ReadView::m_low_limit_no - only used by purge, regular views should not have to snapshot it
- optimise busy waiting in trx_sys_t::snapshot_ids() - it is quite high in profile already
Attachments
Issue Links
- is caused by
-
MDEV-14638 Replace trx_sys_t::rw_trx_set with LF_HASH
- Closed
-
MDEV-14756 Remove trx_sys_t::rw_trx_list
- Closed
-
MDEV-15019 InnoDB: store ReadView on trx
- Closed
-
MDEV-15059 Misc small InnoDB scalability fixes
- Closed
-
MDEV-15104 Remove trx_sys_t::rw_trx_ids and trx_sys_t::serialisation_list
- Closed
-
MDEV-15246 InnoDB: Unknown error code 20: Required history data has been deleted
- Closed