No change in behavior.

Check for PTHREAD_MUTEX_ROBUST_NP definition (this doesn't work
on Linux/glibc because they used an enum). Zero out mutex before
initing.

Don't leave them uninit'd if they now point at a valid DUP node

If we know there are no sub-DBs and no overflow pages, skip leaf scan.

make sure C_DEL gets reset in subcursor after it moves.

Howard Chu authored Jan 02, 2016 and Hallvard Furuseth committed Jan 09, 2016

wsize was being truncated to 32bits on Windows.
Only try to write 1GB at a time on Windows64;
larger writes fail with ERROR_WORKING_SET_QUOTA.

Howard Chu authored Dec 19, 2015 and Hallvard Furuseth committed Jan 09, 2016

From 1ba5adb2 "MDB_VL32 preparation".

Let "illegal" branch pages thru on the FreeDB - the condition
is only temporary and will be fixed by the time rebalance finishes.

check for utf8_to_utf16 failures

Sebastien Launay authored Dec 03, 2015 and Howard Chu committed Dec 03, 2015

pthread_mutexattr_setrobust and pthread_mutex_consistent are provided since 2.12 not 2.10:
https://sourceware.org/git/?p=glibc.git;a=commit;h=402cd98775db1478f64c9b0dbe00664b89eb2773
https://sourceware.org/git/?p=glibc.git;a=commit;h=78ee21859939ff75ccf8bbe00499b0c462df2e2d

from da67af1a

After delete/add of a node, other nodes may no longer be
pointing at the data they intended. This can confuse subsequent
fixups.

Only set it if the cursor's current position was deleted

Based on page_touch fixup from ITS#7594 but expanded:
make sure sub-cursors agree with main cursors.

Always reinit mc_pg[0] if cursor is not C_INITIALIZED
It might have a stale value when using nested txns

Always unset C_INIT flag if the cursor's target DB has been deleted

Must remove our spilled pages from parent's dirty list

DUPFIXED fixups needed to occur after separator update.
MDB_RESERVE handling moved after split fixup.

In rebalance/split operations, temporary cursors need to be visible
to propagate fixups

Ignore sub-cursors that shouldn't be fixed up

Set a valid txn so that cursor fixup code works on the shadows

It was reporting spurious errors due to uninit'd cursors

Adjustments can't be skipped, in recursive calls each level must
fixup their own level.