Aliases pointing within the original search scope could cause
the same entry to be returned multiple times. Check for subtree
scope and duplicate scopes.

we already checked for data == NULL, drop unnecessary if

Move CACHEFLUSH, avoid unnecessary if()

Must save/restore mcd cursor if we're doing a scope-based search.

Harmless, but stupid.

Of course, MacOSX only has posix_memalign, and only in recent versions.
(Older versions could use valloc instead. That precludes ever changing
the LMDB pagesize to be different from the OS pagesize.) Not all that
crucial since it only affects mdb_env_copyfd1.

Leaving them in dirty_list caused breakage.  Instead merge them
into me_pghead at the end, when no more pages will be allocated.

This needs to be streamlined in 2.5, current tool API is a mess.

Don't accept config directives for cache DB until the cache backend type
has been set.

db_open/close were not symmetric with init/destroy

Don't let dummy go out of scope

Everything has it. Solaris doesn't have posix_memalign.

rename ppolicy_close -> ppolicy_db_close for consistency

don't free pwcons unless we're actually destroying this DB

Go directly to local backend when fetching local entry

In server mode, make sure the entry was actually ours

Do a cacheflush after writing data pages, separate from meta's cacheflush

They were obsoleted by ITS#6737 and have been redundant ever since.
(commit 15f1e7bd)

Paranoia for 36300668 do the
cacheflush before setting mti_txnid.

FIRST_DUP/LAST_DUP should succeed even on non-duplicate values
PREV_DUP should reset cursor's EOF flag.