All rules

Style

postgresql/snake-case-table-name

Require snake_case table names.

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

Quoted mixed-case identifiers (`"UserAccounts"`) preserve their case and force every caller to quote them — a steady source of `relation does not exist` errors. Unquoted `CamelCase` is silently lowercased by PostgreSQL and passes the rule.

Examples

Incorrect

Incorrect
CREATE TABLE "UserAccounts" (id INT PRIMARY KEY);

Correct

Correct
CREATE TABLE user_accounts (id INT PRIMARY KEY);
Correct
CREATE TABLE UserAccounts (id INT PRIMARY KEY); -- folded to useraccounts

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/snake-case-table-name": [
        "warn",
        {
          allow: [],
        },
      ],
    },
  },
];

Options

allow string[] default: []
Identifiers to exempt from the rule. Useful for tables that must keep an external name (e.g. `KEYWORDS`, vendor schemas).
Try this rule

Edit the SQL — only snake-case-table-name 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 snake-case-table-name — 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