GitLab

Conflicts:
	servers/slapd/back-mdb/id2entry.c

Missing entries need to be checked at runtime too, not just slapcat.
Apparently some people will still try to run slapd even after slapadd
tells them their DB load was invalid.

Missing entries need to be checked at runtime too, not just slapcat.
Apparently some people will still try to run slapd even after slapadd
tells them their DB load was invalid.

Zero out the complete context buffer
From mhardin@symas.com

Emily Backes authored Jan 10, 2013 and Quanah Gibson-Mount committed Jan 16, 2013

Update slapd.overlays.5 manpage index

That's all we have space for in a node record.

Also MDB_MAXKEYSIZE is redefinable at compile time.

Forgot this in 98fe3390

Very large single transactions will fail. It's not just a problem when
nested transactions are used. We could make this dynamically sized,
but I'm not sure what the point is.

This is only a 10% gain, but still worth having for now.

No time to find the bug at the moment.
There's no performance benefit anyway.

If we're operating on the freelist, see if our current pghead
can satisfy the request before giving up and using new pages.

This may possibly trigger ITS#5835 again. Revert if so.

Treat zero-length entries properly (as missing entries) in entry_next()
and entry_get_int().

Lightning Memory-Mapped Database