File: lock_concurrent.test

package info (click to toggle)
mariadb-10.0 10.0.25-0%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 466,160 kB
  • ctags: 182,424
  • sloc: cpp: 1,376,579; ansic: 826,548; perl: 59,653; sh: 36,635; pascal: 32,260; yacc: 14,915; xml: 5,210; sql: 4,660; cs: 4,647; makefile: 4,555; ruby: 4,465; python: 2,282; lex: 1,427; asm: 295; awk: 54; php: 22; sed: 16
file content (52 lines) | stat: -rw-r--r-- 1,008 bytes parent folder | download | duplicates (13)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
#
# READ LOCAL / WRITE CONCURRENT locks.
# This test is separate from the main lock.test
# because the feature is likely to be unsupported.
#

--source have_engine.inc

--source include/count_sessions.inc

SET lock_wait_timeout = 1;

--let $create_definition = a $int_col
--source create_table.inc

LOCK TABLES t1 WRITE CONCURRENT, t1 AS t2 READ;

connect (con1,localhost,root,,);
SET lock_wait_timeout = 1;

# If this statement fails with ER_LOCK_WAIT_TIMEOUT,
# most likely the engine does not support LOCK .. WRITE CONCURRENT
LOCK TABLES t1 READ LOCAL;
if ($mysql_errname)
{
  --let $functionality = LOCK .. WRITE CONCURRENT
  --source unexpected_result.inc
}

UNLOCK TABLES;

connection default;
UNLOCK TABLES;

connection con1;
LOCK TABLES t1 READ LOCAL;

connection default;
LOCK TABLES t1 WRITE CONCURRENT, t1 AS t2 READ;
UNLOCK TABLES;

connection con1;
UNLOCK TABLES;
disconnect con1;

connection default;
DROP TABLE t1;

--source include/wait_until_count_sessions.inc

--source cleanup_engine.inc