Simple scenario:
Process [1]:
session->create(session, "table:test", "key_format=S, value_format=S ");
session->drop(session, "table:test", "");
session->close(session);
Process2:
session->create(session, "table:test", "key_format=S, value_format=S ");
// Do not drop table
session->close(session);
Executing serially [1] [1] [1] [1] ... works fine.
Executing serially [2] [2] [2] [2] ... works fine.
Executing serially [1] [2] causes an error. Specifically session->drop replies that table:test does not exist.
- related to
-
WT-68 Design and implement dump format
- Closed
-
WT-175 race in forced page eviction
- Closed
-
WT-176 race in allocating WT_PAGE_MODIFY structures
- Closed
-
WT-179 the cache isn't empty after verifying WiredTiger.wt
- Closed
-
WT-180 make the connection's default session a real session
- Closed
-
WT-310 overflow blocks may be accessed after deletion
- Closed
-
WT-312 Fast truncate support
- Closed
-
WT-322 table and lsm object statistics
- Closed
-
WT-323 Test concurrent bulk loads
- Closed
-
WT-403 Minor changes to fix uri table display. WT-397
- Closed
-
WT-404 Add check for any calls to strtouq. WT-390
- Closed
-
WT-441 Allow LSM trees to discard the btree handle from the active chunk.
- Closed
-
WT-442 Reconciliation's handling of the page's memory footprint could be improved.
- Closed