← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/locks.rst

  • Committer: Andrew Hutchings
  • Date: 2011-01-08 09:35:11 UTC
  • mto: (2067.1.1 build)
  • mto: This revision was merged to the branch mainline in revision 2068.
  • Revision ID: andrew@linuxjedi.co.uk-20110108093511-upf7b0onx3sa1arr
https://launchpad.net/bugs/700099
Get drizzle build system to support Linux native AIO for InnoDB

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/locks.rst
20
20
 
21
21
If a session should exit, whatever locks it was holding will be deleted.
22
22
 
23
 
.. todo::
24
 
 
25
 
   deleted or released? are locks recursive?
26
 
 
27
23
Please note, get_lock() was designed to be compatible with MySQL. If you
28
24
hold any locks when calling get_lock() they will be released. For this
29
25
reason you may want to consider calling get_locks() instead.
30
26
 
31
27
Information on all barriers can be found in the DATA_DICTIONARY.USER_LOCKS
32
 
table;
 
28
table;
 
 
b'\\ No newline at end of file'