postgresql/consistent-drop-index-concurrently

Why this matters

Plain `DROP INDEX` takes an `ACCESS EXCLUSIVE` lock on the table. `DROP INDEX CONCURRENTLY` waits for current users instead. The `never` style is for migration tools that wrap each step in `BEGIN`/`COMMIT` — concurrent drops cannot run inside a transaction. Non-index `DROP` statements are out of scope.

Examples

DROP INDEX idx_users;

DROP INDEX CONCURRENTLY idx_users;

DROP INDEX CONCURRENTLY IF EXISTS idx_orders;

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

Options

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

`always` (default) requires `CONCURRENTLY`. `never` forbids it.