Why this matters
`VACUUM FULL` takes `ACCESS EXCLUSIVE` and rewrites the whole table, making it unavailable for the duration. For shrinking a bloated table on a live database use `pg_repack` or `pg_squeeze`; a plain `VACUUM` is fine.
Examples
Incorrect
VACUUM FULL users;Correct
VACUUM users;VACUUM ANALYZE 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-vacuum-full": "warn",
},
},
];Options
Edit the SQL — only no-vacuum-full 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-vacuum-full — plus no-syntax-error as a safety net.