File: rocksdb_concurrent_delete_main.inc

package info (click to toggle)
mariadb-10.3 1%3A10.3.34-0%2Bdeb10u1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 531,600 kB
  • sloc: cpp: 1,415,326; ansic: 917,243; perl: 58,570; sh: 43,538; pascal: 39,206; java: 33,919; yacc: 32,096; javascript: 15,655; python: 10,576; ruby: 8,684; xml: 5,957; makefile: 4,893; sql: 3,750; asm: 841; lex: 670; php: 22; awk: 20; sed: 16
file content (30 lines) | stat: -rw-r--r-- 887 bytes parent folder | download | duplicates (5) 
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
 
--source include/have_rocksdb.inc
--source include/have_debug_sync.inc

# This validates the fix for Issue #144.  The problem was that with more
# than one client accessing/deleting the same row there was a possibility
# of client A finding a row (through Next() or Prev()) but the row being
# deleted before the GetForUpdate() call could occur.  When this happened
# a nearly useless error was being returned.

let $order=ASC;
let $comment="";
--source rocksdb_concurrent_delete.inc
--source rocksdb_concurrent_delete_sk.inc

let $order=DESC;
let $comment="";
--source rocksdb_concurrent_delete.inc

let $order=ASC;
let $comment="rev:cf2";
--source rocksdb_concurrent_delete.inc

let $order=DESC;
let $comment="rev:cf2";
--source rocksdb_concurrent_delete.inc

let $index=PRIMARY;
--source rocksdb_concurrent_delete_range.inc
let $index=sk;
--source rocksdb_concurrent_delete_range.inc