postgresql/no-set-not-null

Why this matters

PostgreSQL scans the whole table to verify no nulls, holding `ACCESS EXCLUSIVE` for the duration. The PG ≥ 12 pattern is `ADD CHECK (col IS NOT NULL) NOT VALID` → `VALIDATE CONSTRAINT` → `SET NOT NULL` (PG reuses the validated CHECK and skips the scan).

Examples

ALTER TABLE users ALTER COLUMN email SET NOT NULL;

ALTER TABLE users ADD CONSTRAINT users_email_not_null CHECK (email IS NOT NULL) NOT VALID;

ALTER TABLE users VALIDATE CONSTRAINT users_email_not_null;

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-set-not-null": "warn",
    },
  },
];

Options

This rule has no options.