The final fix for this bug involves writing zeros into the unused bytes of the disk when serializing nodes.  
This is important for two reasons:
 1. It makes the files the same the bit-level.  (The problem showed up because a node of size near 1MB was written, and then the node split, causing the node to shrink, and when the node was written again, some left over bits from the previous node were still on disk.  Then the file compare failed after recovery.)
 1. It causes the file system to actually allocate the space for a node, so that when a node grows, it will all be contiguous on disk.

It has the disadvantage of writing more to disk than we did before, possibly reducing performance.  It probably doesn't matter much, however. 


git-svn-id: file:///svn/tokudb@2916 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2914 c7de825b-a66e-492c-adef-691d508d4ae1

Fixes many problems in {{{test_log10}}}.  There's a memory leak and the recovered files still differ, however.  Addresses #548.

git-svn-id: file:///svn/tokudb@2913 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2912 c7de825b-a66e-492c-adef-691d508d4ae1

Fixes a bug with escalation caught by valgrind.


git-svn-id: file:///svn/tokudb@2904 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2903 c7de825b-a66e-492c-adef-691d508d4ae1

implemented lock escalation MINUS flagging of messy transactions
implemented tests for lock escalation

git-svn-id: file:///svn/tokudb@2902 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2900 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2898 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2895 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2893 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2892 c7de825b-a66e-492c-adef-691d508d4ae1

test_thread_insert doesn't leak memory any more.  The leak is in {{{pthread_exit()}}}.  If you return from the initial function, the leak isn't there.  Fixes #303.

git-svn-id: file:///svn/tokudb@2884 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2883 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2882 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2881 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2880 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2877 c7de825b-a66e-492c-adef-691d508d4ae1

Reordered escalation.
First escalate writes, and only if that succeeds, we escalate the reads.
Now, if we fail during the reads we are still consistent, whereas before
we would need to panic.

git-svn-id: file:///svn/tokudb@2876 c7de825b-a66e-492c-adef-691d508d4ae1

Implemented testing if escalating a range from borderwrite is trivial.

git-svn-id: file:///svn/tokudb@2875 c7de825b-a66e-492c-adef-691d508d4ae1

Started coding lock escalation.
Have several function stubs that need to be implemented.

git-svn-id: file:///svn/tokudb@2874 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2873 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2871 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2870 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2869 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2868 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2866 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2865 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2864 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2855 c7de825b-a66e-492c-adef-691d508d4ae1

Deal with the multithreaded cursor DBT memory allocaiton problem.  Addresses #538.  (I'm going to write a few more tests before calling it fixed.)

git-svn-id: file:///svn/tokudb@2854 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2853 c7de825b-a66e-492c-adef-691d508d4ae1

assert for the BDB behaviour.



git-svn-id: file:///svn/tokudb@2847 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2846 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2845 c7de825b-a66e-492c-adef-691d508d4ae1

create (but not yet implement) functions for lock escalation

git-svn-id: file:///svn/tokudb@2836 c7de825b-a66e-492c-adef-691d508d4ae1

Segrate rollback and recover functions.   Write a brt-level test for the cursor static variable problem.  Addresses #536, #538.

git-svn-id: file:///svn/tokudb@2829 c7de825b-a66e-492c-adef-691d508d4ae1

make {{{test_cursor_2}}} use an environment with {{{DB_THREAD}}} set, since that the MySQL usage.  Addresses #538.

git-svn-id: file:///svn/tokudb@2828 c7de825b-a66e-492c-adef-691d508d4ae1

write iterator for linear range tree

git-svn-id: file:///svn/tokudb@2826 c7de825b-a66e-492c-adef-691d508d4ae1

Uses range iterator (of range trees) to simplify code in lock tree.

This allowed us to deleting 'emergency' version of a function that was not well tested.

git-svn-id: file:///svn/tokudb@2825 c7de825b-a66e-492c-adef-691d508d4ae1