MySQL Bugs: #42065: maria: deadlock_timeout_short and naming conventions

Bug #42065	maria: deadlock_timeout_short and naming conventions
Submitted:	12 Jan 2009 21:35	Modified:	27 Dec 2010 12:25
Reporter:	Peter Gulutzan	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Maria storage engine	Severity:	S4 (Feature request)
Version:	6.1.0-alpha-debug	OS:	Linux (SUSE 10.0 / 32-bit)
Assigned to:		CPU Architecture:	Any

Description:
The variable deadlock_timeout_short
appears to be specifically for Maria.

With other storage engines, I see the
storage engine name as a prefix for the
variable name, for example
falcon_lock_wait_timeout
innodb_lock_wait_timeout
innodb_rollback_on_timeout

I see that for Maria too, sometimes.
For example,
maria_sort_buffer_size 

I conclude that this is an accepted naming
convention, and therefore it is a mistake
to fail to call this variable
maria_deadlock_timeout_short

Other maria variables misbehave similarly.

How to repeat:
show variables like '%timeout%';
show variables like 'maria%';

Thank you for taking the time to write to us, but this is not a bug.

deadlock_timeout_short and others are not maria variables. They are configuration variables of the server-wide deadlock detector. It is expected that storage engines will use it to be able to detect inter-storage-engine deadlocks.

At the moment, only Maria uses it.

Nobody said it was a bug.
I marked it feature request.

Oracle does not sponsor or coordinate active development of Maria storage engine. So interested parties should report bugs and request features in Maria (sorry, Aria now :) at https://bugs.launchpad.net/maria