Description
In the event of a table (table A) with a foreign key referencing a row-level TTL enabled table (table B), users have to avoid the possibility of data contention by filtering out expired rows in their application logic in their queries on table A. This would ensure that the rows tou 5CB8 ched in table A do not contend with the TTL job (in which the job could block workload txns).
In the case where no application logic is performed and the queries on table A are occurring, we see our TTL jobs leave user queries hanging - like with https://github.com/cockroachlabs/support/issues/2786.
This is due to the UserPriority set on TTL deletes; we should investigate any workarounds. One discussed was using a high UserPriority/different UserPriority.
Jira issue: CRDB-35311