Randomly create a bloom filter on an LSM tree chunk before it's first
merge (lsm_bloom_newest) and/or create a bloom filter on the oldest LSM
tree chunk (lsm_bloom_oldest).
Assert the files compare equally, otherwise we won't fail.
whitespace
Add a test where we backup everything, not just a list of targets: it's
a different path inside the engine.
When scanning the global transaction table, ignore IDs older than the published oldest ID: the thread involved will not use the published ID.

refs #683
Don't read both the standard and the command-line CONFIG file, use one
or the other.
fix a comment
Change dhandles to use a singly linked list.  Fix bug in close to
acquire the dhandle lock.  #690
Remove line to set SCHEMA_LOCKED flag instead of taking lock.
Back out 5c6e4e0, we still need to set the flag, that's what the lower
layers check.
Merge pull request #692 from wiredtiger/branch690

dhandle locking during close
Fix assert for special case of read-uncommitted txns. #693
Add a minor comment about what happens if the insert races.
Closes #690.
The wrapped-generation check is only called from serial functions, we know
the page's modify structure is set.
Fix a comment: we no longer track the page's write generations, this
comment should have been fixed in 1027c6de96.
Test the WT_BTREE.modified value before setting it, it's probably a hot
cache line.  (This is the only real change here, the rest is semantic
sugar.)

Set the WT_BTREE.modified value after we've flushed the insert/update
information (I don't think this is a bug, but it feels cleaner).

Flip the default for page-dirty: by default, mark both the tree and the
page dirty.  There are 3 places we have reason not to mark the tree
dirty, add comments for them; clean up the places we were setting the
WT_BTREE.modified value explicitly instead of calling the right modify
function.  This doesn't change the previous behavior, but it's safer --
I want people to have to search for some way to NOT dirty the tree, in
the rare case that's useful.
Regularize a couple of comments.
It's possible to race when deciding if we're making the first update to
a page, which could mess up the cache statistics.   Use the serial lock
to protect that test (specify if we already hold that lock when we call
the __wt_page_modify_set/__wt_page_only_modify_set functions).
Don't bother allocating a WT_PAGE_MODIFY structure if we're not going
to use it.
It doesn't matter if we mark the page or the tree dirty first; collapse
the three page-modify functions back into a pair of functions, one of
which marks the page dirty, the other of which calls the first and then
marks the tree dirty.