docs/reference/rules/avoid-adding-exclusion-constraint.md
Diagnostic Category: lint/safety/avoidAddingExclusionConstraint
Since: vnext
[!NOTE] This rule is recommended. A diagnostic error will appear when linting your code.
Sources:
Adding an exclusion constraint acquires an ACCESS EXCLUSIVE lock.
Exclusion constraints require a full table scan to validate and block all reads
and writes while held. Unlike other constraints, there is no concurrent alternative.
Use SET lock_timeout to limit the impact on concurrent operations.
This also applies to exclusion constraints defined inline in CREATE TABLE.
alter table my_table add constraint my_excl exclude using gist (col with &&);
code-block.sql:1:1 lint/safety/avoidAddingExclusionConstraint ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
! Adding an exclusion constraint acquires an ACCESS EXCLUSIVE lock.
> 1 │ alter table my_table add constraint my_excl exclude using gist (col with &&);
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 │
i There is no concurrent alternative for exclusion constraints. Use SET lock_timeout to limit the impact on concurrent operations.
alter table my_table add constraint my_check check (col > 0) not valid;
{
"linter": {
"rules": {
"safety": {
"avoidAddingExclusionConstraint": "error"
}
}
}
}