All rules

Style

postgresql/no-group-by-ordinal

Disallow positional `GROUP BY` references (e.g., `GROUP BY 1`).

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

Same fragility as positional `ORDER BY`: reordering the SELECT list silently shifts the grouping to a different column, producing plausible-looking but wrong aggregates. Reference the column by name or by the grouping expression.

Examples

Incorrect

Incorrect
SELECT category, count(*) FROM items GROUP BY 1;
Incorrect
SELECT region, category, sum(amount) FROM sales GROUP BY 1, 2;

Correct

Correct
SELECT category, count(*) FROM items GROUP BY category;
Correct
SELECT region, category, sum(amount) FROM sales GROUP BY region, category;

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-group-by-ordinal": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-group-by-ordinal 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-group-by-ordinal — 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