postgresql/consistent-create-or-replace

Why this matters

Two valid stances exist: (a) always use `CREATE OR REPLACE` so re-running a migration is idempotent, or (b) never use it so unintended overwrites are surfaced as `relation already exists`. Pick one with the `style` option; the rule auto-fixes either way. `CREATE TABLE` / `CREATE INDEX` are out of scope (they don't support `OR REPLACE`).

Examples

CREATE FUNCTION fn() RETURNS void LANGUAGE SQL AS '';

CREATE PROCEDURE p() LANGUAGE SQL AS '';

CREATE VIEW v AS SELECT 1;

CREATE OR REPLACE FUNCTION fn() RETURNS void LANGUAGE SQL AS '';

CREATE OR REPLACE PROCEDURE p() LANGUAGE SQL AS '';

CREATE OR REPLACE VIEW v AS SELECT 1;

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/consistent-create-or-replace": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

style "always" | "never" default: "always"

Which stance to enforce. `always` (default) requires `OR REPLACE` so re-running is idempotent. `never` forbids `OR REPLACE` so unintended overwrites are surfaced.