[Date Prev][Date Next]
(ITS#7844) LMDB Delete Cursor inconsistencies
Full_Name: Armon Dadgar
Submission from: (NULL) (188.8.131.52)
When using a transaction across multiple named tables, it seems that if I am
iterating and deleting I can trigger a condition that causes some rows to be
missed by the cursor.
There is a test case here that can reproduce it:
You can run it using:
go run test.go mdb_table.go
Here is one of my test runs:
In that test, I would expect all 128 entries to be deleted, but only 43 are
before the cursor stops returning new rows.