All rules

Safety

postgresql/require-if-exists

Require `IF EXISTS` on every `DROP` statement.

  • Type suggestion
  • Recommended off
  • Fixable no

Why this matters

An `IF EXISTS` `DROP` is idempotent — re-running the migration after a partial run does not error. Covers `DROP TABLE`, `DROP INDEX`, `DROP FUNCTION`, `DROP TRIGGER`, `DROP DATABASE`, `DROP SCHEMA`, `DROP ROLE`. Other statements are out of scope.

Examples

Incorrect

Incorrect
DROP TABLE foo;
Incorrect
DROP INDEX idx_foo;
Incorrect
DROP FUNCTION fn();

Correct

Correct
DROP TABLE IF EXISTS foo;
Correct
DROP INDEX IF EXISTS idx_foo;
Correct
DROP FUNCTION IF EXISTS fn();

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/require-if-exists": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only require-if-exists is enabled.

Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.

0 errors 0 warnings parse 0ms · rules 0ms
Diagnostics

No issues found.

2 rules enabled.

Rule under test require-if-exists — plus no-syntax-error as a safety net.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17