[YSQL][Read Committed] Transaction in Read Committed Isolation level fails with conflicts with higher priority transaction

[shishir2001-yb]

Jira Link: DB-12186

Description

Version: 2.23.0.0-b609

Currently, a transaction in Read Committed Isolation with Fail On Conflict (i.e., with Wait On Conflict off) can run into the issue described below. Ideally, we should not throw the error conflicts with higher priority transaction in RC because all transactions have the same priority.

Exception: could not serialize access due to concurrent update (yb_max_query_layer_retries set to 60 are exhausted)\nDETAIL: [Operation failed. Try again (yb/docdb/conflict_resolution.cc:93): e917b9e0-ff11-45b0-be64-f5ae3e0f2d2d conflicts with higher priority transaction: e4f67062-b3cc-49c6-bb21-a2e7fc722eb8 (transaction error 3)]\n

We have just reused the same error message for both < and = in the below snippet

      // READ COMMITTED txns require a guarantee that no txn abort it. They can handle facing a
      // kConflict due to another txn's conflicting intent, but can't handle aborts. To ensure
      // these guarantees -
      //   1. all READ COMMITTED txns are given kHighestPriority and
      //   2. a kConflict is raised even if their_priority equals our_priority.
      if (our_priority <= their_priority) {
        return MakeConflictStatus(
            our_transaction_id, transaction.id, "higher priority", GetTabletMetrics());

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.