postgresql/no-add-check-constraint-without-not-valid

Why this matters

`ALTER TABLE t ADD CONSTRAINT c CHECK (...)` validates every existing row inside an `ACCESS EXCLUSIVE` lock. The two-step pattern (`ADD CONSTRAINT ... NOT VALID` then `VALIDATE CONSTRAINT` in a separate transaction) holds only `SHARE UPDATE EXCLUSIVE` during validation. Non-CHECK constraints are out of scope.

Examples

ALTER TABLE t ADD CONSTRAINT c CHECK (x > 0);

ALTER TABLE t ADD CONSTRAINT c CHECK (x > 0) NOT VALID;
ALTER TABLE t VALIDATE CONSTRAINT c;

Configure it

// eslint.config.js
import postgresql from "eslint-plugin-postgresql";

export default [
  {
    files: ["**/*.sql"],
    languageOptions: {
      parser: postgresql.configs.recommended.languageOptions.parser,
    },
    plugins: { postgresql },
    rules: {
      "postgresql/no-add-check-constraint-without-not-valid": "error",
    },
  },
];

Options

This rule has no options.