postgresql/no-add-unique-constraint-directly

Why this matters

`ALTER TABLE ... ADD CONSTRAINT ... UNIQUE (...)` builds the unique index inline under `ACCESS EXCLUSIVE`. The lock-friendly form is to build the index out-of-band with `CREATE UNIQUE INDEX CONCURRENTLY`, then promote it via `ADD CONSTRAINT ... UNIQUE USING INDEX <name>`. Non-UNIQUE constraints are out of scope.

Examples

ALTER TABLE t ADD CONSTRAINT uq_t_email UNIQUE (email);

CREATE UNIQUE INDEX CONCURRENTLY idx_t_email ON t (email);
ALTER TABLE t ADD CONSTRAINT uq_t_email UNIQUE USING INDEX idx_t_email;

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-unique-constraint-directly": "error",
    },
  },
];

Options

This rule has no options.