Skip to content

crosscluster/logical: transactional LDR REGIONAL BY ROW implicit partition columns produce wrong unique lock IDs #172376

Description

@jeffswenson

Describe the problem

CollectKeyColumnIDs on an implicitly partitioned unique index includes
crdb_region, but uniqueness is enforced across regions — two txns in different
regions taking the same unique value get different lock hashes.

Impact

Missed conflicts on REGIONAL BY ROW unique indexes. Reachability uncertain (is
RBR intended to be supported for txn LDR?); if not, it needs an explicit
validation gate rather than silent mis-locking.

Code references

Suggested fix

If RBR is unsupported, add an explicit validation gate at txn-mode creation. If
supported, exclude implicit partition columns from unique lock derivation.

Epic CRDB-65552

Jira issue: CRDB-65611

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-logical-data-replicationC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.O-agentFiled by an AI agent; usually the result of a human/agent investigation sessionT-cdc

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions