The visibility of a fast truncate is based on the commit timestamp that is performed in the truncate operation and whereas the obsolete of the fast truncate page is based on the durable timestamp of the truncate operation if the commit and durable timestamps are different and it is true for the prepared transactions.

Currently, the WiredTiger code uses the comit timestamp to check the obsoleteness of the page. Change it to use the durable timestamp can avoid the scenarios where the oldest timestamp falls between the commit timestamp and durable timestamp.