GitLab

On DUPSORT DBs, must initialize xcursor regardless of whether
caller requested its data.

FreeBSD 11 supports robust process-shared POSIX mutexes,
but requires them to be explicitly destroyed before munmap

This reverts commit 0e895ffe.
Was not an LMDB bug.

mdb_load wasn't properly inserting escaped backslashes into the data.
mdb_dump wasn't escaping backslashes when generating printable output.

Kris Zyp authored Apr 15, 2019 and Howard Chu committed Apr 16, 2019

Broken in ITS#8756

Ka Ho Ng authored Feb 17, 2019 and Howard Chu committed Feb 17, 2019

Always call GetModuleHandleW() with Unicode string, as mdb_fopen() is
calling CreateFileW() already.

Bump up number of keys for which we use fine-grained splitpoint search

The official macro is __ANDROID__; ANDROID may or may not be defined.

To allow reloading of custom-sorted DBs from mdb_dump

and enforce exclusive access to environment. Also fix txn_begin/pick_meta
to use correct meta page, and reset the flag after successful commit.

Unnecessary since these are DUPs, the key will always be the same

Avoid stomping on flags from 1st readhr invocation

Use GetProcAddress at runtime, avoid buildtime NTDLL link issues

This patch fixes liblmdb builds on Solaris and derivatives by defining
_POSIX_PTHREAD_SEMANTICS

This checks XCURSOR_INITED() and fixes the mn_flags check.

* Check NUMKEYS(), similar to f34b61f9
  "ITS#8722 fix FIRST_DUP/LAST_DUP cursor bounds check".
* Move XCURSOR_INITED() into XCURSOR_REFRESH().  This adds a check in
  mdb_cursor_put, below /* converted, write the original data first */.
* Factor mc_ki[] out to XCURSOR_REFRESH().
* Replace an mc_pg[] with mp which is equal (mdb_cursor_del0).