https://bugs.openldap.org/show_bug.cgi?id=8803
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |1.0.0
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• 7a1f36d5
by Nir Soffer at 2026-04-24T20:19:46+01:00
ITS#8803 LMDB: add tool option to disable locking
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8192
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• ba6e0018
by Howard Chu at 2026-04-24T18:07:42+01:00
ITS#8192 fix prev commit
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8192
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |1.0.0
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• bf5c4e0f
by Howard Chu at 2026-04-24T16:05:40+01:00
ITS#8192 LMDB: define new error codes to avoid errno abuse
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8579
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• cf52db2b
by Howard Chu at 2026-04-23T18:55:06+01:00
ITS#8579 LMDB: all descriptors should have O_CLOEXEC
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9027
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |1.0.0
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• 63698faf
by Howard Chu at 2026-04-22T19:22:56+01:00
ITS#9027 LMDB: expose address of memory map
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8174
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Target Milestone|--- |1.0.0
Resolution|--- |TEST
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• d0fcfd3d
by Howard Chu at 2026-04-22T17:24:28+01:00
ITS#8174 LMDB: fixes for mdb_drop(MAIN_DBI)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8590
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
Target Milestone|--- |0.9.36
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.RE/0.9:
• f06db92f
by Lorenz Bauer at 2026-04-22T19:33:30+01:00
ITS#8590 LMDB: Use F_SETNOSIGPIPE on OS X
mdb.master:
• 66be07b7
by Lorenz Bauer at 2026-04-22T19:30:57+01:00
ITS#8590 LMDB: Use F_SETNOSIGPIPE on OS X
mdb.master3:
• 81697bc2
by Lorenz Bauer at 2026-04-22T19:32:45+01:00
ITS#8590 LMDB: Use F_SETNOSIGPIPE on OS X
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7794
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• 43670420
by Howard Chu at 2026-04-22T11:26:00+01:00
ITS#8165 LMDB: add soname, lib version
• 0734803d
by Howard Chu at 2026-04-22T12:45:11+01:00
ITS#8165 more for prev commit
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8165
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.master3:
• 43670420
by Howard Chu at 2026-04-22T11:26:00+01:00
ITS#8165 LMDB: add soname, lib version
• 0734803d
by Howard Chu at 2026-04-22T12:45:11+01:00
ITS#8165 more for prev commit
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10275
Issue ID: 10275
Summary: mdb_load could use a parameter to pass batch size
Product: LMDB
Version: 0.9.21
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: tools
Assignee: bugs(a)openldap.org
Reporter: gkwicker(a)amazon.com
Target Milestone: ---
Created attachment 1037
--> https://bugs.openldap.org/attachment.cgi?id=1037&action=edit
Patch to mdb_load.c in version 0.9.21
mdb_load is very slow when ingesting a large db. The attached patch (0.9.21
but will apply to other versions with modification) allows the user to pass a
batch size to be used instead of the default value of 100. Changing the batch
size to a larger value improves ingestion speed.
I, Gary Wicker, hereby place the following modifications to OpenLDAP Software
(and only these modifications) into the public domain. Hence, these
modifications may be freely used and/or redistributed for any purpose with or
without attribution and/or other notice.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6462
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• ed30d827
by OndÅ™ej KuznÃk at 2026-04-16T02:13:15+00:00
ITS#6462 libldap: Add ldap_domain2hostlist_proto
• 3ebfd3e8
by OndÅ™ej KuznÃk at 2026-04-16T02:13:15+00:00
ITS#6462 clients: Enable DNS SRV resolution for ldaps connections
• 69c2a54b
by OndÅ™ej KuznÃk at 2026-04-16T02:13:15+00:00
ITS#6462 slapd-dnssrv: Enable DNS SRV resolution for ldaps
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8739
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.RE/0.9:
• 856c1fa8
by Howard Chu at 2026-04-15T20:04:30+01:00
ITS#8739 lmdb: No fdatasync on FreeBSD 11.0 and older
mdb.master:
• f759f0fc
by Howard Chu at 2026-04-15T20:03:57+01:00
ITS#8739 lmdb: No fdatasync on FreeBSD 11.0 and older
mdb.master3:
• b2cfdd23
by Howard Chu at 2026-04-15T20:03:06+01:00
ITS#8739 lmdb: No fdatasync on FreeBSD 11.0 and older
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8824
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb.RE/0.9:
• 790035a2
by Howard Chu at 2026-04-15T18:18:39+01:00
ITS#8824 mdb_dump: cleanup check for MDB_SUCCESS
mdb.master:
• 331ba439
by Howard Chu at 2026-04-15T18:17:55+01:00
ITS#8824 mdb_dump: cleanup check for MDB_SUCCESS
mdb.master3:
• 5b3df476
by Howard Chu at 2026-04-15T18:18:44+01:00
ITS#8824 mdb_dump: cleanup check for MDB_SUCCESS
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8386
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
mdb/RE0.9:
• 9a647381
by Philipp Storz at 2026-04-15T17:32:58+01:00
ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc
mdb.master:
• 7b5ffe1b
by Philipp Storz at 2026-04-15T17:32:14+01:00
ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc
mdb.master3:
• 06680017
by Philipp Storz at 2026-04-15T17:33:05+01:00
ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9011
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Howard Chu <hyc(a)openldap.org> ---
Added to git mdb.master3, mdb.RE/1.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9011
--- Comment #4 from code(a)doriantaylor.com ---
I was trying to determine why I got a notification for this bug, and I see now
that it was because I filed a later one which was marked duplicate.
Indeed, my remarks on issue 9188 constitute why a language binding would need
to know if a transaction was read-only. In the Ruby bindings for LMDB which I
now maintain, it's easy to find situations like
db.transaction(true, &proc) # `true` enables read-only
...where `proc` itself does another transaction. I have semi-fixed this so
read-only transactions "nest" by making the call a no-op if a transaction is
already active, but it's still possible for read-write transactions to find
their way inside read-only ones. So being able to create a `txn.readonly?`
predicate would be useful for programmers downstream to better orient
themselves.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8394
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|SUSPENDED |WORKSFORME
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8394
--- Comment #8 from bdallen(a)nps.edu <bdallen(a)nps.edu> ---
Hi Howard,
Please forgive me. Yes, I started this ten years ago on another project
which was resolved. When I saw your new post
https://bugs.openldap.org/show_bug.cgi?id=8394#c3 I assumed they were
related. They are not.
Good to hear you are still supporting LMDB. It worked very well for me.
Cheers,
-Bruce
On 4/28/26 10:03, openldap-its(a)openldap.org wrote:
> NPS WARNING: *external sender* verify before acting.
>
>
> https://bugs.openldap.org/show_bug.cgi?id=8394
>
> --- Comment #7 from Howard Chu <hyc(a)openldap.org> ---
> (In reply to bdallen(a)nps.edu from comment #6)
>> Hi Howard,
>>
>> I did not submit issue 8394. I suspect somebody in Pico Technical
>> Support Team submitted this in my name in response to SUPPORT-63913
>> Crashing bug in pypicosdk that I submitted to support(a)picotech.com. I
>> responded to you incorrectly believing I was working with Pico Technical
>> Support.
>>
>> Meanwhile, I can offer some information:
>> 1) You cannot reproduce this bug without having a PicoScope connected to
>> a USB port and without "sudo apt install picoscope" per
>> https://www.picotech.com/downloads/linux and without "pip install
>> pypicosdk".
>> 2) I would suspect the core dump reported is the result of object
>> mismanagement in Python bindings in pypicosdk except that someone in
>> Pico Technical Support has stated the fault is line 6590 of mdb.c.
>>
>> Please let me know if I can help.
>>
>> Regards,
>> -Bruce
> Thanks for the information. That initial report is from 10 years ago, and LMDB
> v0.9.18 is long since obsolete.
>
> We're about to release v1.0.0. It would probably be worth seeing if you can
> reproduce the problem with that release candidate.
> https://git.openldap.org/openldap/openldap/-/tree/mdb.RE/1.0?ref_type=heads
>
> For what it's worth, using clang-20's -fsanitize=type sanitizer, it shows some
> potential problems in v0.9.18 but it only gives false positives with the 1.0
> branch.
>
> --
> You are receiving this mail because:
> You reported the issue.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8394
--- Comment #7 from Howard Chu <hyc(a)openldap.org> ---
(In reply to bdallen(a)nps.edu from comment #6)
> Hi Howard,
>
> I did not submit issue 8394. I suspect somebody in Pico Technical
> Support Team submitted this in my name in response to SUPPORT-63913
> Crashing bug in pypicosdk that I submitted to support(a)picotech.com. I
> responded to you incorrectly believing I was working with Pico Technical
> Support.
>
> Meanwhile, I can offer some information:
> 1) You cannot reproduce this bug without having a PicoScope connected to
> a USB port and without "sudo apt install picoscope" per
> https://www.picotech.com/downloads/linux and without "pip install
> pypicosdk".
> 2) I would suspect the core dump reported is the result of object
> mismanagement in Python bindings in pypicosdk except that someone in
> Pico Technical Support has stated the fault is line 6590 of mdb.c.
>
> Please let me know if I can help.
>
> Regards,
> -Bruce
Thanks for the information. That initial report is from 10 years ago, and LMDB
v0.9.18 is long since obsolete.
We're about to release v1.0.0. It would probably be worth seeing if you can
reproduce the problem with that release candidate.
https://git.openldap.org/openldap/openldap/-/tree/mdb.RE/1.0?ref_type=heads
For what it's worth, using clang-20's -fsanitize=type sanitizer, it shows some
potential problems in v0.9.18 but it only gives false positives with the 1.0
branch.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8394
--- Comment #6 from bdallen(a)nps.edu <bdallen(a)nps.edu> ---
Hi Howard,
I did not submit issue 8394. I suspect somebody in Pico Technical
Support Team submitted this in my name in response to SUPPORT-63913
Crashing bug in pypicosdk that I submitted to support(a)picotech.com. I
responded to you incorrectly believing I was working with Pico Technical
Support.
Meanwhile, I can offer some information:
1) You cannot reproduce this bug without having a PicoScope connected to
a USB port and without "sudo apt install picoscope" per
https://www.picotech.com/downloads/linux and without "pip install
pypicosdk".
2) I would suspect the core dump reported is the result of object
mismanagement in Python bindings in pypicosdk except that someone in
Pico Technical Support has stated the fault is line 6590 of mdb.c.
Please let me know if I can help.
Regards,
-Bruce
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8394
--- Comment #5 from Howard Chu <hyc(a)openldap.org> ---
(In reply to bdallen(a)nps.edu from comment #4)
> Here is the code I used which generates the core dump in round 2. It
> should complete 10 rounds then say "Done.":
>
> import pypicosdk as psdk
>
> def test(n):
> Â Â print(n, "checkpoint.a")
> Â Â scope = psdk.psospa()
> Â Â print(n, "checkpoint.b")
> Â Â scope.open_unit()
> Â Â print(n, "checkpoint.c")
> Â Â scope.close_unit()
> Â Â print(n, "checkpoint.d")
>
> if __name__ == "__main__":
> Â Â for i in range(1, 11):
> Â Â Â Â test(i)
> Â Â print("Done.")
>
>
I have no idea how to install pypicosdk. You're going to have to provide
sufficient info for someone to actually reproduce the software you're running.
What I see here https://github.com/picotech/pyPicoSDK
"
Go to PicoTech downloads picotech.com/downloads
Find your PicoScope in the list and click through
Download and install PicoSDK for your operating system
"
Since I have no PicoScope I have no idea what to install.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8335
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
--- Comment #8 from Howard Chu <hyc(a)openldap.org> ---
Fixed in git
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8502
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
Nothing worth changing here.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8916
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
The problem is that Windows doesn't let you use a readonly mapping that extends
beyond the length of a file. This is noted in commit
5eb25c5cb9122fcc016e770bcc1f033e3a9d2a0f and
9d75a82ae10fdcee80b8b8e82c6ef9b6ab83dc47.
Since the env is readonly we aren't expecting the file to grow. There's no
provision for detecting that the underlying file is changing, in a readonly
env.
This is just a limitation of Windows so there's no workaround. Don't mix
readonly envs with readwrite envs.
--
You are receiving this mail because:
You are on the CC list for the issue.