specifies a percentage of the tree to skip over before retrieving each
new record. If next_random_sample_percent is configured, we first
retrieve a random record from the tree as a whole, and on subsequent
retrievals, skip forward the specified percentage of the tree; if
next_random_sample_percent is not configured, we use the previous method
of choosing a new leaf page from the entire tree on each retrieval.
Clarify bulk and next-random cursor documentation: there are several
methods allowed on bulk and next-random cursors (for example, reset,
reconfigure and close), don't try to list them. Instead reference the
principle method the application is expected to use (insert for bulk
cursors, next for next-random cursors).
Make cursor-open with next_random configured fail for column-store
objects, waiting until the next method is called seems unkind.
Rework the static random-cursor tests to smoke-test both forms of random
cursors.
- "join:" URI handling added to WT_SESSION::open_cursor, added WT_SESSION::join.
- Added support for in-memory bloom filters.
- Minor fix to cur_dump_close CURSOR_API_CALL.
- Some refactoring in __wt_{curindex,curtable}_get_value() to allow them
to be called internally.
- Use new macro JOINABLE_CURSOR_API_CALL() instead of CURSOR_API_CALL()
to trap illegal calls to joined cursor.
- __wt_curtable_open now takes an owning cursor arg.
- Added __wt_struct_unpack_size() and __wt_struct_repack()
I was seeing internal pages grow to contain over 70,000 entries. Which
makes reconciliation of child pages very expensive. Be more aggressive
about splitting internal pages.
Allows applications to maintain a low proportion of dirty pages in
the cache, while allowing clean pages to utilize the cache.
While here, alter the minimum allowed dirty trigger and target to
be set as low as 5 percent. Which may be desired for huge caches.
refs SERVER-16737, WT-1350
e Please enter the commit message for your changes. Lines starting
* Allow a snapshot from a running transaction, but enforce that
the transaction is and remains read only.
* Enhance test cases
* Fixup locking, so a call to snapshot appears atomic (i.e: drop and create
are wrapped in a single lock)
* Fixup naming in named snapshot source file to be consistent.
