postgresql/consistent-reindex-concurrently

Why this matters

Non-concurrent `REINDEX TABLE` takes a `SHARE` lock that blocks writers for the duration; `REINDEX INDEX` takes `ACCESS EXCLUSIVE`. PG ≥ 12 introduced `REINDEX (...) CONCURRENTLY`, which builds a parallel index and swaps without blocking writers. The `never` style is for migration tools that wrap each step in `BEGIN`/`COMMIT` — `CONCURRENTLY` cannot run inside a transaction.

Examples

REINDEX TABLE users;

REINDEX TABLE CONCURRENTLY users;

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-reindex-concurrently": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

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

`always` (default) requires `CONCURRENTLY`. `never` forbids it so each `REINDEX` can run inside a migration transaction.