postgresql/consistent-timestamptz

Why this matters

Two valid stances exist: (a) require `timestamptz` so the database anchors everything to UTC at storage time and converts on read (avoiding the timezone-naive trap of `timestamp`), or (b) forbid `timestamptz` so the type is consistent across a project that treats every timestamp as UTC at the application layer and doesn't want implicit per-session `TimeZone` conversions. Pick one with the `style` option.

Examples

CREATE TABLE t (created_at TIMESTAMP);

CREATE TABLE t (created_at TIMESTAMPTZ);

CREATE TABLE t (created_at TIMESTAMP WITH TIME ZONE);

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/consistent-timestamptz": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

style "always" | "never" default: "always"

Which stance to enforce. `always` (default) requires `timestamptz` over `timestamp`. `never` requires `timestamp` over `timestamptz` — useful when the application treats every value as UTC and doesn't want implicit per-session conversions.