Skip to content

Loss of committed tuple from secondary index in memtx #7712

@CuriousGeorgiy

Description

@CuriousGeorgiy

Steps to reproduce

os.execute('rm -rf *.snap *.xlog *.vylog 512')

local ffi = require('ffi')
local json = require('json')
local log = require('log')
local txn_proxy = require('txn_proxy')

box.cfg{memtx_use_mvcc_engine = true}

local s = box.schema.space.create('s')
s:create_index('pk')
s:create_index('sk', {parts = {{2}}})

local tx = txn_proxy:new()
tx:begin()

tx('box.space.s:insert{0, 1}')
s:insert{2, 1}

box.internal.memtx_tx_gc(100)

log.info('%s', json.encode(s.index[1]:select({}, {fullscan = true})))

os.exit()

Actual behavior

 ---
[[]]
...

Expected behavior

 ---
[[[2, 1]]]
...

Metadata

Metadata

Labels

2.10Target is 2.10 and all newer release/master branchesbugSomething isn't workingmemtxmvcc

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions