dict_store_statistics() should commit mtr for each record's update

Bug #791092 reported by Yasufumi Kinoshita
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Unassigned
5.1
Fix Released
Undecided
Unassigned
5.5
Fix Released
Medium
Unassigned

Bug Description

dict_store_statistics() (called when innodb_use_sys_stats_table is enabled)
updates several records in SYS_STATS on 1 mtr.

But, "btr_pcur_move_to_next_user_rec(&pcur, &mtr);" might release the x_lock of the block and might cause problem.

So, need
"
mtr_commit(&mtr);
mtr_start(&mtr);
btr_pcur_restore_position(BTR_MODIFY_LEAF, &pcur, &mtr);
"
for each change.

Related branches

Changed in percona-server:
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
importance: Undecided → Medium
status: New → Confirmed
Changed in percona-server:
status: Confirmed → Fix Committed
Stewart Smith (stewart)
Changed in percona-server:
milestone: none → 5.5.13-20.4
Revision history for this message
Alexey Kopytov (akopytov) wrote :

In 5.1 the fix was released in 5.1.57-12.8. Updating the target milestone accordingly.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1199

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.