All rules

Safety

postgresql/no-alter-column-type

Warn on `ALTER COLUMN ... TYPE` — can rewrite the table under ACCESS EXCLUSIVE.

  • Type problem
  • Recommended warn
  • Fixable no

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

Incorrect
ALTER TABLE users ALTER COLUMN id TYPE bigint;

Correct

Correct
ALTER TABLE users ADD COLUMN id_new bigint;
Correct
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

This rule has no options.

Try this rule

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.

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

No issues found.

2 rules enabled.

Rule under test no-alter-column-type — 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