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

Rename innodb_adaptive_hash_index_num

Bug #689451 reported by Vadim Tkachenko
6
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
Percona Server moved to https://jira.percona.com/projects/PS 5.5-20beta

Bug Description

I propose to rename
innodb_adaptive_hash_index_num
to
innodb_adaptive_hash_instances
by analogy with innodb_buffer_pool_instances

Vadim Tkachenko (vadim-tk)
Changed in percona-server:
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 5.5-20beta
Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

"adaptive_hash_index" is full name. should not to be trimmed.
And, even "partitions" is accepted (It may be more natural word to separated index). But "instances" is not accepted for me as natural for "index".
Basically, innodb_buffer_pool_"instances" is something wrong for me. I think "instance" should be used more large component (like mysqld process etc..).

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

And innodb_buffer_pool_"instances" are not independent each other. Basically it should not called as "instances"

Vadim Tkachenko (vadim-tk)
Changed in percona-server:
status: New → Fix Committed
Vadim Tkachenko (vadim-tk)
Changed in percona-server:
status: Fix Committed → Fix Released
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-2580

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

Other bug subscribers

Remote bug watches

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