https://bugs.openldap.org/show_bug.cgi?id=9225
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |SUSPENDED
--- Comment #1 from Howard Chu hyc@openldap.org --- It's already available in LMDB 1.0 but it's not really interesting in back-mdb itself. The interesting use case is for backglue; if a client requests a transaction that spans multiple backends then backglue must use 2 phase commit to arrange it on all of the independent backends. There's also still an atomicity issue: after all of the target backends Prepare successfully, their final commits may not all happen in the same instant since they still need to be requested individually on each backend. It kind of implies that a global lock is needed on each target backend that won't be released until all of the commit requests finish.
I suggest we postpone this.