no-rename-column · eslint-plugin-postgresql

Why this matters

The rename completes atomically in the database, but every running app instance that still references the old name starts erroring the moment the migration runs. Use add → dual-write → backfill → drop across separate deploys.

Examples

Incorrect

ALTER TABLE users RENAME COLUMN email_address TO email;

Correct

ALTER TABLE users ADD COLUMN email text;

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-rename-column": "warn",
    },
  },
];

Options

This rule has no options.

Edit the SQL — only no-rename-column 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-rename-column — plus no-syntax-error as a safety net.