Submitted by: Boltik Evgeny (bolt)

It happens only if the index key was removed (concurrently or by the cooperative GC) after reading it but before validating it using the fetched record. Only DESC indices are affected, the issue also depends on index key values. The bug seems to be inherited from InterBase.

Simplified example (leaf page layout):

key A, length 23, points to record 120006 (old version to be GCed)
key B, length 22, points to record 119054
key C, length 22, points to record 119535
key D, length 22, points to record 120006 (last committed version)

Key A gets GCed while reading and disappears, but key B is skipped and only records for C and D are returned. The second execution (with no GC involved) correctly returns {B, C, D}. The issue manifests itself only if key B has all its 22 bytes equal to key A (which is one byte longer).

Commits: e8bd26a 16e356f 3b7b316

====== Test Details ======

Waiting for suggest how to implement this test, letter to/from dimitr 06-may-2016 22:51.