Re: AW: AW: (ITS#8777) [LMDB] Closing read cursor uses already freed transaction (MDB_VL32)

[hyc@symas.com]

Markus Junginger wrote:
> I perfectly see that MDB_VL32 is the superior as a feature. On the other
> hand I'm a bit worried that it may hold up LMDB development for use cases
> you refer to as obsolete yourself.
> 
> While there are workarounds for this particular bug (which we applied),

There was never a bug here. The doc is quite explicit
http://www.lmdb.tech/doc/group__mdb.html#ga73a5938ae4c3239ee11efa07eb22b882

After txn_abort the only valid call on a still-open cursor is cursor_renew, 
not cursor_close.
-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/