All rules

Performance

postgresql/require-limit

Require a LIMIT clause on SELECT.

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

Defends against accidentally pulling the entire table over the wire. Best applied to ad-hoc query files; report-style queries that intentionally aggregate everything will fight the rule and should disable it locally.

Examples

Incorrect

Incorrect
SELECT * FROM users;
Incorrect
SELECT name, email FROM users WHERE active = true;

Correct

Correct
SELECT * FROM users LIMIT 100;
Correct
SELECT name, email FROM users WHERE active = true LIMIT 50;

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/require-limit": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only require-limit 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 require-limit — 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