Separate LSM work unit types from flags. #1208
Add push/pop macros for the different queues. #1208
Add length tracking and assertions for lsm work queues. #1208 #1230
Tweak the LSM manager aggressive update alg and server trigger. #1230
row-search releases "child" on error, and we were updating "child" to
point to pages that were the wrong pages to release on error. The code
in row-random and column-search don't require the same changes, but I
made them so the code continues to look roughly the same in all three
functions.
Check tree's queue length and remove global assertion. #1230
Remove manager struct lengths and add in per-queue lengths to stats.
Restore some of the manager conditional.  My changes broke normal
switchng and its intent is covered in the aggressiveness changes. #1230
Merge pull request #1232 from wiredtiger/cleanup-row-search-error-handling

Fix row-search error handling.
Add stat to count number of times we reach queue_ref maximum. #1230
Comments, cleanup and fix an error path. #1208
Merge pull request #1231 from wiredtiger/lsm-cleanup

Cleanup LSM code and update how the LSM manager pushes work units onto the queue. Refs #1230
Don't assign WT_ITEMs in example code, some WT_ITEM fields are private.
Whitespace.
Simplify __wt_connection_close(), there's no reason for it to have the
loops to discard extension handles.
typo
The boundary-next field points to the next boundary structure we were
going to use, but there's no requirement that value be incremented
before reconciliation updates the structure it points to, that is,
there's no guarantee elements of the next boundary structure are still
unchanged. Be defensive, clean up the "next" structure as well as the
ones we know we used.  Reference #1239.

Minor cleanups to clean out the structure more completely.
whitespace
whitespace
Quit trying to clean up the boundary structures on exit, instead
initialize each boundary array element right before it's about to
be used. This is probably slightly more work, but it's less likely
to break in the field, the code to allocate a new boundary item
has to be correct otherwise we'd hit the end of the array and drop
core. Reference #1239.
Merge pull request #1241 from wiredtiger/initialize-boundary-at-use

Reconciliation boundary initialization cleanup.
Merge branch 'develop' into cursor-uri-protect