no-cluster · eslint-plugin-postgresql

Why this matters

`CLUSTER` takes `ACCESS EXCLUSIVE` and rewrites the whole table just like `VACUUM FULL`. PostgreSQL does not keep rows clustered as you continue to write, so every subsequent `CLUSTER` must rewrite everything again. Use `pg_repack --order-by` for online clustering.

Examples

Incorrect

CLUSTER users USING users_pkey;

Correct

VACUUM 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/no-cluster": "warn",
    },
  },
];

Options

This rule has no options.

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