postgresql/consistent-identity-over-serial

Why this matters

Serial pseudo-types create a separately-owned sequence that does not round-trip cleanly through `pg_dump` and does not honor column-level privileges. `GENERATED ... AS IDENTITY` is the SQL-standard replacement and has been the PostgreSQL team's recommendation since version 10. Pick one direction with the `style` option.

Examples

CREATE TABLE t (id BIGSERIAL);

CREATE TABLE t (id SERIAL);

CREATE TABLE t (id BIGINT GENERATED ALWAYS AS IDENTITY);

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/consistent-identity-over-serial": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

style "always" | "never" default: "always"

`always` (default) requires identity columns over serial pseudo-types. `never` requires the serial pseudo-types for projects that keep compatibility with tooling that does not understand identity columns.