From: Hallvard Furuseth <hallvard@openldap.org>
Date: Thu, 7 Nov 2013 22:38:15 +0000 (+0100)
Subject: Fix MDB_MAXKEYSIZE doc: Account for MDB_DUPSORT.
X-Git-Tag: OPENLDAP_REL_ENG_2_4_38~8^2~3
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=fc87d405f1636d2241306584189f6b1266bbb833;p=openldap

Fix MDB_MAXKEYSIZE doc: Account for MDB_DUPSORT.

A node may need room for [key, subpage with 2 items] = 3 keys.
---

diff --git a/libraries/liblmdb/mdb.c b/libraries/liblmdb/mdb.c
index 19d5f20a5d..484ab2ce04 100644
--- a/libraries/liblmdb/mdb.c
+++ b/libraries/liblmdb/mdb.c
@@ -373,7 +373,7 @@ static txnid_t mdb_debug_start;
 	 *
 	 *	We require that keys all fit onto a regular page. This limit
 	 *	could be raised a bit further if needed; to something just
-	 *	under (page size / #MDB_MINKEYS).
+	 *	under (page size / #MDB_MINKEYS / 3).
 	 *
 	 *	Note that data items in an #MDB_DUPSORT database are actually keys
 	 *	of a subDB, so they're also limited to this size.