All rules

Safety

postgresql/no-having-without-group-by

Disallow `HAVING` without `GROUP BY`; the predicate belongs in `WHERE`.

  • Type problem
  • Recommended error
  • Fixable no

Why this matters

PostgreSQL accepts `HAVING` without `GROUP BY` and collapses the query to a single aggregate row over the whole table — almost never what the author meant. If the predicate is row-level, put it in `WHERE`. If it's aggregate-level, add a `GROUP BY`.

Examples

Incorrect

Incorrect
SELECT count(*) FROM users HAVING count(*) > 1;

Correct

Correct
SELECT category, count(*) FROM items GROUP BY category HAVING count(*) > 1;
Correct
SELECT count(*) FROM users WHERE active;

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-having-without-group-by": "error",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-having-without-group-by is enabled.

Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.

0 errors 0 warnings parse 0ms · rules 0ms
Diagnostics

No issues found.

2 rules enabled.

Rule under test no-having-without-group-by — plus no-syntax-error as a safety net.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17