CockroachDB index should to store caveats

[jzelinskie]

Problem Statement

A production system recommended the following index: CREATE INDEX ON relation_tuple (namespace, relation, object_id, userset_relation) STORING (caveat_name, caveat_context);

Solution Brainstorm

This is the closest to our primary key constraint and should improve overall check performance.

[jzelinskie]

This can also be applied to our reverse index, too

[lalalalatt]

I just made a pull request (#1988) and I’m seeking some clarification on how this change can enhance the check performance.

From my understanding, there is only one type of SQL query used in the check request, and its WHERE condition is the same as the new index. Would a standard index suffice to improve the query speed? Additionally, could you please explain why STORING (caveat_name, caveat_context); is necessary?

Thank you for your assistance!