I did:
{{{
svn merge -r3229:3230 https://svn.tokutek.com/tokudb/tokudb.558
}}}


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

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

{{{
svn merge -r3061:3225 https://svn.tokutek.com/tokudb/tokudb.558
}}}

Fixes #630.
Addresses #558.


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

ignoring the non-fast version of the lock trees

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

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

Lock escalation for reads.
Also, bugfix with lock escalation for writes, we sometimes forgot to set 
OUT_OF_LOCKS to FALSE

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

Range trees now return ranges in sorted order

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

Fixed a bug in tokudb.
In a NO_DUP database, if we have a cursor pointing to an element,
and then insert (overwrite) an element with the same key but larger (as per cmp func)
data, then DB_NEXT should NOT return the newly inserted element.. it should
return the element with the next larger key.

The opposite error also existed for DB_PREV.

We rewrite the flag of DB_NEXT/DB_PREV to DB_NEXT_NODUP and DB_PREV_NODUP
when there are no duplicates.

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

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

We were reading error codes of malloc incorrectly.
errno is not valid unless you know you had an error.

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

Fixes memory leak (in a test)

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

Merge all of ticket 567 into trunk

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

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

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

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

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

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

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

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

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

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

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

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

Add the first two tests for {{{DB_ENV->log_archive}}}.  Fix up some memory leaks.  Add {{{LSN*}}} to all the {{{toku_log_*}}} functions so that {{{toku_logger_txn_begin}}} can use the LSN as a txnid.  Addresses #75, #83, #392.

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

{{{DB_ENV->log_archive}}} understands checkpoints, but not live transactions.  Addresses #75, #83, #392.

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

make {{{DB_ENV->log_archive}}} return something (but it's not quite right).  Clean up the serialization of the brt header.  Fix up {{{DB_ENV->txn_checkpoint}}} (but it's not quite right).  Addresses #75, #83, #392.

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

error code for running out of locks

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

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

test_abort2 works up until a lock tree problem.  I think the test and abort mechanisms are right now.  I'll close #556 but file a new bug (#569).  Fixes #556.  Addresses #569.

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

Addresses #554
When lock trees close before transactions do (that touch them), we can crash
or have memory corruption.

Now, when lock trees close, they alert all transactions that they have disappeared.

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

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

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

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

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

while investigating 554, came across this issue of not checking for proper value
This MAY fix 554, but we doubt it.

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

Lock escalation causes all lock trees (all dbs in an environment)
to escalate their locks.
This is useful, since we can have one lock tree/db holding 99% of the locks
and then we run out of locks on a different lock tree.

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

Fixed memory leak during closing of lock tree managers.

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

Fixes memory leak (just in test) of locktree managers.

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

Lock tree manager keeps track of all the lock trees so we can loop through them.

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

'Lock tree manager' object created to hold data shared by all lock trees
i.e. Current number of locks (per env) and max locks (per env)
Uses functions to change max_locks.
Added tests for lock tree manager.


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