Percona Server moved to https://jira.percona.com/projects/PS

Document and rename INNODB_ROW_LOCK_NUMBERS

Bug #721615 reported by Vadim Tkachenko on 2011-02-19

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Percona Server moved to https://jira.percona.com/projects/PS	Fix Released	Undecided	Unassigned
	5.5	Fix Released	High	Unassigned	Percona Server moved to https://jira.percona.com/projects/PS 5.5-20.1rc "CTO edition"

we have INNODB_ROW_LOCK_NUMBERS status variable

from source code it is
+ export_vars.innodb_row_lock_numbers
+ = lock_sys->rec_num;

as I understand it is count of records locks applied at given point of time.

If my understanding is correct we should rename it to
Innodb_current_row_locks

Vadim Tkachenko (vadim-tk) on 2011-02-19

Changed in percona-server:
assignee:	nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone:	none → 5.5-21rc
status:	New → Confirmed
importance:	Undecided → High

Vadim Tkachenko (vadim-tk) on 2011-02-22

Changed in percona-server:
status:	Confirmed → Won't Fix
importance:	High → Undecided
assignee:	Yasufumi Kinoshita (yasufumi-kinoshita) → nobody
milestone:	5.5-20.1rc → none

Revision history for this message

Stewart Smith (stewart) wrote on 2012-06-13:

fix released back in early 5.5

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-25:

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

Revision history for this message

Peter Schwaller (peter-schwaller) wrote on 2018-01-30:

Test update. Ignore.

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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