Use regular fsync() if we think this commit grew the DB file.

We actually compare the new key against the last key, to prevent
corruption.

The concurrency restriction is on threads within a single process.
Multiple processes can use mdb_dbi_open without affecting each other.

More fallout from 4d02c741:
Don't modify another thread's write txn. Reinit me_txn0 fully.

Howard Chu authored 10 years ago and Hallvard Furuseth committed 10 years ago

fstat returns -1, not an errno. Move code into its own function
for reuse.

Howard Chu authored 10 years ago and Hallvard Furuseth committed 10 years ago

More fallout from 4d02c741

Jean-Christophe DUBOIS authored 10 years ago and Hallvard Furuseth committed 10 years ago

Signed-off-by: Jean-Christophe DUBOIS <jcd@tribudubois.net>

Leonid Yuriev authored 10 years ago and Hallvard Furuseth committed 10 years ago

TRIVIA - lmdb: clean testdb-dir while "make test".

When reusing the main write txn

Free writer txn on env_close

Change retry to num times 60.  Testing shows that on a known dataset, this has the same growth behavior as 2.4.39, while num times 20 resulted in significant growth.

Leave it in main env struct, it doesn't need to be rolled back
with nested txns.

Don't walk the readers table unless we really need to.

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

Move CACHEFLUSH, avoid unnecessary if()

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.