Problem
The ASC Fast Truncate implementation does not work on standby nodes because it needs to write fast truncate information directly to the standby table which violates the core principle in which any update/insert operations can’t be done in standby mode. A new standby fast truncate design will be adopted to enable fast truncate.

The new fast truncate design will live in-between the ingest and stable table. The read/write path way will be ingest -> truncate -> stable. During step-up we also need to drain all truncates onto the stable table. This is a little tricky because we also replay all truncate operations on the ingest table.

What needs to be done
During step-up, we drain all relevant truncates to the stable table. Follow technical design on details on how this could work. Furthermore python tests should validate this behaviour.