WiredTiger does not currently support local tables on disaggregated storage connections, except for the internal tables such as WiredTiger.wt and WiredTigerHS.wt. However, local tables are becoming a very useful tool for debugging, such as to enable the mirrored mode in test/format. It is also very likely that supporting local tables will increase the code's overall robustness, given that we already have some internal local tables.

We should thus weigh the cost and the risk of supporting local tables against their benefit, and decide the level of support that we would like to provide. This can range from keeping the status quo and not supporting them at all, all the way to full support. We can also consider an intermediate level of support, which will be just enough to improve testing. In the meantime, let's use this epic to collect all tickets that we would have to be done to provide full support, so that we can make a better informed decision.

If we proceed with this, we would most likely only support timestamped local tables, not logged tables, as we don't currently have any compelling use cases for them in testing or otherwise, and as supporting them will require us to implement an even more complicated checkpoint handling than what is described in this epic.