hlc: panic on update with synthetic timestamp #57684
Labels
A-kv-transactions
Relating to MVCC and the transactional model.
A-multiregion
Related to multi-region
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Needed for non-blocking transactions: #52745.
An HLC clock should never be updated with a synthetic timestamp. This is part of how we will validate that we are keeping the clock time domain and the transaction time domain separate.
The text was updated successfully, but these errors were encountered: