Choosing Between statement_timeout and pg_cancel_backend for Safe Query Cancellation in Distributed YugabyteDB Transactions
Goal: ensure that cancelling a long‑running YSQL statement also aborts any associated distributed transaction promptly across all tablet leaders, preventing stale locks that could block concurrent workloads. Constraints: statement_timeout is automatic and scoped to a single statement but counts network latency toward the timeout, which can cause false‑positi
yugabytedb