[MDEV-31346] trx_purge_add_undo_to_history() is not optimal - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.5, 10.6, 10.11, 10.4(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 11.0(EOL)
Fix Version/s: 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2
Component/s: Storage Engine - InnoDB
Labels:
- performance

Description

The function trx_purge_add_undo_to_history(), which is called after each transaction commit or rollback that had modified persistent tables, is not optimal. It calls trx_undo_set_state_at_finish() in a different compilation unit and evaluates a condition on undo->state several times. We could get a small performance improvement by simplifying this.

Attachments

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2023-05-25 14:12

Updated:: 2023-06-07 13:31

Resolved:: 2023-05-26 14:01

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.