Hi Dean, On 12 Sep 2026, Dean Rasheed wrote: > possible to fix this without a potentially expensive re-fetch.
Unlike v4, v5 also takes SIREAD locks on index pages, which can cause extra false positives. The additional retries could outweigh saving the fetch. Also, violationOK includes preliminary checks of deferred exclusion constraints, so v5 adds predicate locking there at SERIALIZABLE too. Is that needed? Could we restrict the new snapshot to arbiter probes? Thank you! Best regards, Andrey Borodin.
