no-with-recursive-without-limit · eslint-plugin-postgresql

Why this matters

A `WITH RECURSIVE` query without a terminating `LIMIT` can run unbounded if a join condition is wrong or a base case is missing. Adding an outer `LIMIT` puts a hard ceiling on the rows produced.

Examples

Incorrect

WITH RECURSIVE r AS (
  SELECT 1 AS n
  UNION ALL
  SELECT n + 1 FROM r
) SELECT * FROM r;

Correct

WITH RECURSIVE r AS (
  SELECT 1 AS n
  UNION ALL
  SELECT n + 1 FROM r
) SELECT * FROM r LIMIT 10;

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-with-recursive-without-limit": "error",
    },
  },
];

Options

This rule has no options.

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