All rules

Safety

postgresql/no-distinct-on-without-order-by

Require ORDER BY alongside `SELECT DISTINCT ON (...)` so the surviving row is deterministic.

  • Type problem
  • Recommended error
  • Fixable no

Why this matters

Without `ORDER BY`, PostgreSQL keeps an arbitrary row from each group of `DISTINCT ON` — the result depends on scan order and changes silently across plan or stats updates. Pair `DISTINCT ON` with an `ORDER BY` whose leading columns match.

Examples

Incorrect

Incorrect
SELECT DISTINCT ON (customer_id) customer_id, amount FROM orders;

Correct

Correct
SELECT DISTINCT ON (customer_id) customer_id, amount
FROM orders
ORDER BY customer_id, created_at DESC;
Correct
SELECT DISTINCT customer_id FROM 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/no-distinct-on-without-order-by": "error",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-distinct-on-without-order-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-distinct-on-without-order-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