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
DROP TABLE foo;DROP INDEX idx_foo;DROP FUNCTION fn();Correct
DROP TABLE IF EXISTS foo;DROP INDEX IF EXISTS idx_foo;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
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.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
require-if-exists — plus no-syntax-error as a safety net.