All rules

Syntax

postgresql/no-syntax-error

Detect PostgreSQL syntax errors.

  • Type problem
  • Recommended error
  • Fixable no

Why this matters

Surfaces every parse error from libpg-query as a single lint diagnostic. Without this rule the plugin would silently skip un-parseable files, which is exactly the case where a human reader needs the loudest possible signal.

Examples

Incorrect

Incorrect
-- typo: should be SELECT
INVALID_KEYWORD * FROM users;
Incorrect
SELECT * FROM WHERE id = 1;

Correct

Correct
SELECT * FROM users WHERE id = 1;

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-syntax-error": "error",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-syntax-error 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.

1 rule enabled.

Rule under test no-syntax-error — 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