/*
* __wt_btcur_range_truncate --
* Discard a cursor range from the tree.
*/
int
__wt_btcur_range_truncate(WT_CURSOR_BTREE *start, WT_CURSOR_BTREE *stop)
{
WT_BTREE *btree;
WT_CURSOR_BTREE *cbt;
WT_DECL_RET;
WT_SESSION_IMPL *session;
cbt = (start != NULL) ? start : stop;
session = (WT_SESSION_IMPL *)cbt->iface.session;
btree = cbt->btree;
/*
* For recovery, we log the start and stop keys for a truncate
* operation, not the individual records removed. On the other hand,
* for rollback we need to keep track of all the in-memory operations.
*
* We deal with this here by logging the truncate range first, then (in
* the logging code) disabling writing of the in-memory remove records
* to disk.
*/
if (FLD_ISSET(S2C(session)->log_flags, WT_CONN_LOG_ENABLED))
WT_RET(__wt_txn_truncate_log(session, start, stop));
switch (btree->type) {
case BTREE_COL_FIX:
WT_ERR(__cursor_truncate_fix(
session, start, stop, __cursor_col_modify));
break;
case BTREE_COL_VAR:
WT_ERR(__cursor_truncate(
session, start, stop, __cursor_col_modify));
break;
case BTREE_ROW:
/*
* The underlying cursor comparison routine requires cursors be
* fully instantiated when truncating row-store objects because
* it's comparing page and/or skiplist positions, not keys. (Key
* comparison would work, it's only that a key comparison would
* be relatively expensive. Column-store objects have record
* number keys, so the key comparison is cheap.) Cursors may
* have only had their keys set, so we must ensure the cursors
* are positioned in the tree.
*/
if (start != NULL)
WT_ERR(__wt_btcur_search(start));
if (stop != NULL)
WT_ERR(__wt_btcur_search(stop));
WT_ERR(__cursor_truncate(
session, start, stop, __cursor_row_modify));
break;
}
err: if (FLD_ISSET(S2C(session)->log_flags, WT_CONN_LOG_ENABLED))
WT_TRET(__wt_txn_truncate_end(session));
return (ret);
}
/*
* __wt_btcur_range_truncate --
* Discard a cursor range from the tree.
*/
int
__wt_btcur_range_truncate(WT_CURSOR_BTREE *start, WT_CURSOR_BTREE *stop)
{
WT_BTREE *btree;
WT_DECL_RET;
WT_SESSION_IMPL *session;
session = (WT_SESSION_IMPL *)start->iface.session;
btree = start->btree;
WT_STAT_DATA_INCR(session, cursor_truncate);
/*
* For recovery, log the start and stop keys for a truncate operation,
* not the individual records removed. On the other hand, for rollback
* we need to keep track of all the in-memory operations.
*
* We deal with this here by logging the truncate range first, then (in
* the logging code) disabling writing of the in-memory remove records
* to disk.
*/
if (FLD_ISSET(S2C(session)->log_flags, WT_CONN_LOG_ENABLED))
WT_RET(__wt_txn_truncate_log(session, start, stop));
switch (btree->type) {
case BTREE_COL_FIX:
WT_ERR(__cursor_truncate_fix(
session, start, stop, __cursor_col_modify));
break;
case BTREE_COL_VAR:
WT_ERR(__cursor_truncate(
session, start, stop, __cursor_col_modify));
break;
case BTREE_ROW:
/*
* The underlying cursor comparison routine requires cursors be
* fully instantiated when truncating row-store objects because
* it's comparing page and/or skiplist positions, not keys. (Key
* comparison would work, it's only that a key comparison would
* be relatively expensive, especially with custom collators.
* Column-store objects have record number keys, so the key
* comparison is cheap.) The session truncate code did cursor
* searches when setting up the truncate so we're good to go: if
* that ever changes, we'd need to do something here to ensure a
* fully instantiated cursor.
*/
WT_ERR(__cursor_truncate(
session, start, stop, __cursor_row_modify));
break;
}
err: if (FLD_ISSET(S2C(session)->log_flags, WT_CONN_LOG_ENABLED))
__wt_txn_truncate_end(session);
return (ret);
}
