We noticed quite a few use cases, intentional or not, of creating multiple tables with different timestamps within the same storage transaction, while working on consistent wt table creation project. For example, when creating config.analyzeShardKeySplitPoints, the collection and the _id index are created with a different timestamp from that of the TTL index.

Historically, it's known to be potentially problematic to perform multi-timestamp operations when a DDL operation exist in a storage transaction. The new schema epoch support for table creation exposed this latent issue. We should check if these use cases should be fixed.