All rules
Safety
postgresql/
Warn on `ALTER COLUMN ... TYPE` — can rewrite the table under ACCESS EXCLUSIVE.
Why this matters
PostgreSQL may need to rewrite every row (and every index) under an `ACCESS EXCLUSIVE` lock to change a column's type. For non-trivial tables, add a new column, dual-write, backfill, and swap — or wrap the conversion in a separate, scheduled migration.
Examples
Incorrect
ALTER TABLE users ALTER COLUMN id TYPE bigint;Correct
ALTER TABLE users ADD COLUMN id_new bigint;ALTER TABLE users ALTER COLUMN status SET DEFAULT 'active';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-alter-column-type": "warn",
},
},
]; Options
Edit the SQL — only no-alter-column-type 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
no-alter-column-type — plus no-syntax-error as a safety net.