Bug #46851 Description of plugin interface not complete for table locking.
Submitted: 21 Aug 2009 8:18 Modified: 18 Jan 2010 14:17
Reporter: Horst Hunger Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:azalea OS:Any
Assigned to: MC Brown CPU Architecture:Any
Tags: API, description, plugin
Triage: Needs Triage: D3 (Medium)

[21 Aug 2009 8:18] Horst Hunger
The implementation of store_lock is not sufficient for locking, means to get a crash e.g. in the server methods handing the INSERT statement. The reference to get_share and free_share means lot of analysis basically not necessary to understand the mechanism. 
Missing is a description of the functions thr_lock_init, thr_lock_delete and thr_lock_data_init and their purpose within the code completed by an example to avoid crashes in the server.

How to repeat:
Take out the function "thr_lock_data_init" of the ha_tse.cc and start the test "tse_insert_simple". 

Suggested fix:
see above.
[21 Aug 2009 8:25] Horst Hunger
Forgotten mention: take "mysql-azalea-wl4939".
[21 Aug 2009 14:32] Horst Hunger
see also bug#46858.
[24 Aug 2009 8:50] Horst Hunger
Stefan, I changed the category as it is a document in forge and hope that there will be someone feeling responsible.
[24 Aug 2009 9:19] Sveta Smirnova
Thank you for the report.

Verified as described: descriptions don't exists at http://forge.mysql.com/wiki/MySQL_Internals_Custom_Engine
[3 Sep 2009 7:10] Horst Hunger
Changed it to documentation as is text in Forge contains the issues see also bug 47009.
[18 Jan 2010 14:17] MC Brown
This bug has been promoted to a WorkLog item, and is now part of: