-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Btree
-
Storage Engines - Foundations
-
28.163
-
SE Foundations - 2026-08-04
-
5
When picking up a new layered table during checkpoint pickup, the engine should assert that the new table's btree ID does not conflict with any existing btree ID already registered in the connection.
Without this check, a create/drop/create sequence on a pure follower can leave a stale btree ID that aliases an unrelated tree on the next pickup.
See FIXME-WT-14730 in src/conn/conn_layered_checkpoint_pick_up.c (the "Verify that there is no btree ID conflict" comment). Related: WT-17746 (handle table drop during checkpoint pickup).