Soft deletion marks a record as deleted while retaining it in the database, typically with a deletion timestamp. That preserves recoverability, but it also makes deletion behavior part of every relevant query and index decision. section 7.6
Treat soft deletion as a schema-and-query investigation:
- Check which queries must exclude deleted rows; an apparently correct query can become unsafe when the deletion condition is omitted. section 7.6
- Inspect indexes against the resulting filter shapes rather than assuming the schema explains its own performance. section 7.6
- Account for write amplification: each added index speeds selected reads but adds work to inserts and indexed updates. section 7.6
A production-scale warning
The Booking table has eight indexes because bookings are read frequently and created rarely. Reusing that pattern for an append-only audit log would make writes much more expensive for an infrequent search. section 7.6


