So they can be reused, and avoid unnecessary page_searches

Bug was caused by postalAddressNormalize sending 0-length values
to UTF8StringNormalize.

Detected by valgrind

Well, just like in back-bdb in 2005, it only slowed things down
on larger LDIFs.

Sub-pages need room to grow...

NULL out env->pghead before writing it, so that its pages can't be used
to satisfy the write.

Only for DUPFIXED DBs. Still could do better.

Missed a MDB_RESERVE case

When putting a record, just make space for the data, don't copy it.
(Not compatible with MDB_DUPSORT, since the actual data is needed
to determine the insert location.)

Skip the original cursor that made the change

Rich Megginson authored 13 years ago and Howard Chu committed 13 years ago

PEM nss is not thread safe when establishing the initial connection
using SSL_ForceHandshake.  Create a new mutex - tlsm_pem_mutex - to
protect this function call.
The call to SSL_ConfigServerSessionIDCache() is not thread-safe - move it
to the init section and protect it with the init mutex.

Only worry if consumer has newer state for our SID. Fixes breakage
caused by ITS#6606.

Consumer should never get NO_SUCH_OBJECT for an Add to the underlying DB
during Persist phase.

Must not let the underlying DB generate its own.