openldap-bugs

openldap-bugs@openldap.org

1 participants
21484 discussions

[Issue 7772] liblmdb sub-page growth when adding existing data
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=7772 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |TEST Status|UNCONFIRMED |RESOLVED --- Comment #5 from Howard Chu <hyc(a)openldap.org> --- fixed in git mdb.master3, mdb.master, mdb.RE/0.9 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7974] LDBM's "laggard reader" flaw still present, in continue of ITS#7904
by openldap-its＠openldap.org 26 Apr '26

26 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=7974 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #8 from Howard Chu <hyc(a)openldap.org> --- Fixing this implicitly inside LMDB is the wrong place. The calling app has to make the decision whether they can cope with breaking an atomic read txn into multiple pieces or not. Most applications that take a read txn expect it to stay atomic for the entire duration of their operation. Likewise, the calling apps are the only ones that can decide whether it's safe to kill any of their processes. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9360] New: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
by openldap-its＠openldap.org 26 Apr '26

26 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=9360 Issue ID: 9360 Summary: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: spam(a)markandruth.co.uk Target Milestone: --- I have 2 python scripts writing to a database (lmdb 0.9.26, py-lmdb 0.98) and 5-10 lua processes (with lightningmdb module which uses lmdb 0.9.22) which are long-running serving queries from the database. The database seems fine, not corrupted, and the python writes still working all the time. But periodically (perhaps 10-20% of the time), in a way I am unable to reliably reproduce, when the lua starts up every time a query is issued txn dbi_open returns "MDB_BAD_TXN: Transaction must abort, has a child, or is invalid". A direct restart of the processes does not fix this issue, however stopping lua+python and then starting again after a 5-20s wait usually fixes the issue. This has been reproduced over multiple servers but I'm at a loss as to how to debug this any further? -- You are receiving this mail because: You are on the CC list for the issue.

1 7

[Issue 8748] New feature for LMDB
by openldap-its＠openldap.org 26 Apr '26

26 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8748 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX Severity|normal |enhancement --- Comment #7 from Howard Chu <hyc(a)openldap.org> --- No substantial benefit - the caller should only be attempting to write because they have data that they need to persist. There is nothing useful they can do in the meantime if the txn_begin returns "this would block". -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8250] Allowing transaction to be created in the reset state
by openldap-its＠openldap.org 26 Apr '26

26 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8250 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9011] add mdb_txn_flags()
by openldap-its＠openldap.org 25 Apr '26

25 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=9011 --- Comment #3 from christopher(a)gmerlin.de <christopher(a)gmerlin.de> --- I don't remember the exact reason why I needed this function. But I can offer general remarks. OCaml is a strictly statically typed language. The lmdb binding attaches phantom types to the lmdb data types: a rw/ro type variable to transactions and a dup/nodup type variable to databases. This allows catching some errors like writes with a read-only transaction at compile time. A possible use of mdb_txn_flags() could be to check an _runtime_ that those invariants are not broken when a raw transaction handle (without phantom types) is imported into the typed binding. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8250] Allowing transaction to be created in the reset state
by openldap-its＠openldap.org 24 Apr '26

24 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8250 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|TEST |--- Status|RESOLVED |UNCONFIRMED --- Comment #6 from Howard Chu <hyc(a)openldap.org> --- (In reply to Howard Chu from comment #5) > Added to mdb.master3 4cd8e451679511c8fbeff68f8a97cbe7b1268b48 > > Please test. Then again, will probably revert this. It adds several lines of code to a core function, all to avoid 2 lines of code in the caller. It doesn't make sense to do this. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8803] [PATCH] Add -L option for using external locking
by openldap-its＠openldap.org 24 Apr '26

24 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8803 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |TEST Severity|normal |enhancement Status|UNCONFIRMED |RESOLVED --- Comment #2 from Howard Chu <hyc(a)openldap.org> --- Added to mdb.master3 in 7a1f36d51a27a8b638e470551cff99302cfa5048 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8250] Allowing transaction to be created in the reset state
by openldap-its＠openldap.org 24 Apr '26

24 Apr '26

1 0

[Issue 8250] Allowing transaction to be created in the reset state
by openldap-its＠openldap.org 24 Apr '26

24 Apr '26

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs