https://bugs.openldap.org/show_bug.cgi?id=10395
kero <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1129|0 |1 is obsolete| | --- Comment #13 from kero <[email protected]> --- Created attachment 1130 --> https://bugs.openldap.org/attachment.cgi?id=1130&action=edit Allow multiple nested read transactions from a write transaction review from comment #12 I have found the issue: I was no longer allocating a list for dirty and free pages, but assigning NULL to them was not the solution. I now share the parents' lists with the RDONLY nested children transactions. What do you think? > I'm unsure about allowing nested read transactions from non-NOTLS > environments since they can't be moved between threads. It's already possible > to read using a write transaction in a single thread. I'd prefer to keep the > current code if it works for normal read transactions, and allow nested read > transactions only from NOTLS environments, returning EINVAL or MDB_BAD_TXN > otherwise. What do you think? > Note that I'll have to update the no-longer-ambiguous comment to specify this > restriction on the transactions part: environment must be opened with > MDB_NOTLS to allow for nested read transactions. I implemented the above proposal and updated the comment to clarify that it is only possible to create nested read transactions from NOTLS environments. Thank you for the review again, and sorry for the little hiccup here. Have a nice week, kero -- You are receiving this mail because: You are on the CC list for the issue.
