| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
time, replace it with calls to __wt_txn_update_check, and remove the
calls entirely when there's no WT_UPDATE structure and so no possibility
of detecting a collision.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
in the WT_ITEM's memory.
Found by valgrind reporting "Source and destination overlap in memcpy".
|
|
|
|
|
| |
../../../../ext/test/memrata/memrata.c:2612: error: unused variable ‘kvs_options’
../../../../ext/test/memrata/memrata.c:2612: error: unused variable ‘p’
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Wtperf configuration enhancements.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
../../../bench/wtperf/wtperf.c: In function ‘connection_reconfigure’:
../../../bench/wtperf/wtperf.c:797:18: error: conversion to ‘size_t’ from ‘long int’ may change the sign of the result [-Werror=sign-conversion]
../../../bench/wtperf/wtperf.c: In function ‘config_opt_file’:
../../../bench/wtperf/wtperf.c:1213:19: error: conversion to ‘size_t’ from ‘long int’ may change the sign of the result [-Werror=sign-conversion]
../../../bench/wtperf/wtperf.c: In function ‘config_opt_usage’:
../../../bench/wtperf/wtperf.c:1348:15: error: conversion to ‘size_t’ from ‘int’ may change the sign of the result [-Werror=sign-conversion]
../../../bench/wtperf/wtperf.c: In function ‘indent_lines’:
../../../bench/wtperf/wtperf.c:1517:16: error: conversion to ‘size_t’ from ‘long int’ may change the sign of the result [-Werror=sign-conversion]
cc1: all warnings being treated as errors
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
examples/c/ex_all.c
src/cursor/cur_ds.c
src/cursor/cur_file.c
src/include/wiredtiger.in
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
configured on/true by default, and should only be set if you want
non-standard behavior.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
disk-image is mapped into memory (unmap on page discard), is in allocated
memory (free on page discard), is in memory belonging to a caller (ignore on
page discard), or isn't set at all (ignore on page discard).
We've been trying to figure out which based on the state of WT_PAGE.dsk and
a single flag, and that's not enough. Use two explicit flags, one for
mapped memory and one for allocated memory, and neither flag is set for the
latter two states.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
the wt utility's load command. Change the flag's name, add tests for
the flag to the test suite, make a note in the upgrading docs.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
key/value points into the tree or out of the tree.
|
| | | |
| | | |
| | | |
| | | | |
refs #607
|
| | | |
| | | |
| | | |
| | | | |
refs #607
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is required to support the following sequence:
- set_key
- KEY_APP flag set
- search
- success, RET flags set
- remove
- key copied, RET flag stays set
- deadlock, RET flags cleared
- retry remove
- fails: neither KEY_APP or KEY_RET is set
refs #607
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
function
cur_file.c:268: warning: '__key_data' may be used uninitialized in this function
cur_file.c:268: warning: '__value_size' may be used uninitialized in this function
cur_file.c:268: warning: '__key_size' may be used uninitialized in this function
cur_file.c:268: warning: '__recno' may be used uninitialized in this function
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
that when a cursor's key or value are pointing at internal memory (which is
what the RET flag indicates), that memory is only safe while the cursor
keeps a page referenced. As soon as the cursor releases the page (which
happens at the beginning of most operations), it could be evicted and the
memory could become invalid.
Make the test for whether or not a WT_ITEM.data field references inside the
WT_ITEM's allocated memory a bit more complicated: overflow items will have
data fields that point inside the allocated memory, not at the start of it.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
key/data information, move the handling of WT_CURSTD_{KEY,VALUE}_{APP,RET}
flags out of the btree code and into the cursor code. Reference #607.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Add the "loadtext" command to the help/usage output.
Sort the command parsing switch statement alphabetically.
|
| | | |
| | | |
| | | |
| | | | |
failed. Add code to test and enhance test_schema02 to check.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Expand multiline usage messages to format nicely.
refs #593
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove flagval for random, random_range implies this.
refs #593
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added config_opt_usage() that prints all options/default values/descriptions.
Removed command line options that are available via -o/-O.
refs #593
|
| | | | |
|