All rules

Performance

postgresql/no-leading-wildcard-like

Warn on `LIKE`/`ILIKE` patterns that begin with `%`; they force sequential scans.

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

A pattern like `'%foo'` or `'%foo%'` cannot use a plain B-tree index and forces PostgreSQL into a sequential scan. Use a `pg_trgm` GIN index or full-text search if substring matching is required.

Examples

Incorrect

Incorrect
SELECT id FROM users WHERE email LIKE '%@example.com';
Incorrect
SELECT id FROM users WHERE name ILIKE '%smith%';

Correct

Correct
SELECT id FROM users WHERE email LIKE 'admin@%';
Correct
SELECT id FROM users WHERE email = 'admin@example.com';

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-leading-wildcard-like": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-leading-wildcard-like 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-leading-wildcard-like — 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