On 21.10.19 17:14, Howard Chu wrote:
> I believe this was fixed by commit=20
> 7edf504106c61639a89b9a4e5987242598196932 in mdb.master.=20
I can not confirm that this works.
This is the stack trace where MDB_TXN_FULL is still returned with lates=
mdb.master (note: line numbers shown here are off by 60 compared
if (tl.mid >=3D MDB_TRPAGE_MAX)
=C3=82=C2=A0=C3=82=C2=A0=C3=82=C2=A0 return MDB_TXN_FULL;
Debugger shows tl.mid to be 4095.
You're free to define MDB_TRPAGE_MAX to a larger value. It just means
you increase the chance of overrunning the 2GB available address space.
There's no magic, you can't fit every 64bit database workload into only
a 32bit address space. When your transactions are too large, the normal
thing to do is commit more often so they don't grow so large.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/