SQLSTATE 22009Severity lowLab verified

Incident brief

Time zone displacement out of range

A timestamptz literal whose explicit UTC offset lies outside the valid range (about -15:59 to +15:59) raises this data exception; +16:00 is out of range.

Reproduced on PostgreSQL 18.4Verified 2026-07-24 (isolated lab, PostgreSQL 18.4)Reviewed by Verified against PostgreSQL 18.4 in an isolated lab environment

In 10 seconds

What: Time zone displacement out of range
What triggers it: Write a TIMESTAMP WITH TIME ZONE literal with an explicit offset beyond the allowed range, such as +16:00.
The fix: Use a valid UTC offset (within about +/-15:59).
Proof: Reproduced on PostgreSQL 18.4 → A single SELECT reproduces SQLSTATE 22009; the +16:00 displacement is rejected while the literal is parsed.

The fix

What to do right now

The immediate, application-level response to this error.

Use a valid UTC offset (within about +/-15:59).
Fix the source data or the offset generator so displacements stay in range; the server stores in UTC and renders in the session zone.

Fix — SQL

-- Use a UTC offset within the valid range.
SELECT TIMESTAMP WITH TIME ZONE '2026-01-01 12:00:00+02:00';

Diagnose

See it live on the server

Run these against the affected instance to confirm the diagnosis before you act.

Standard triage — not specific to this error

These are canonical PostgreSQL system-catalog queries, shown as SQL to run. No sample output is attached because this is general triage, not a captured lab transcript.

This SQLSTATE does not have an error-specific live snapshot yet. These are the canonical system-catalog queries you run against the affected server to see the problem in real time — standard triage, not a reproduced transcript.

What is running right now

Active backends, how long each has been running, and what it is waiting on.

SELECT pid,
       state,
       wait_event_type,
       wait_event,
       now() - query_start AS running_for,
       left(query, 80)     AS query
FROM   pg_stat_activity
WHERE  state <> 'idle'
  AND  pid <> pg_backend_pid()
ORDER  BY running_for DESC NULLS LAST;

Who is blocking whom

Turn raw blocking PIDs into the actual queries on both sides of the wait.

SELECT blocked.pid    AS blocked_pid,
       blocked.query  AS blocked_query,
       blocking.pid   AS blocking_pid,
       blocking.query AS blocking_query
FROM   pg_stat_activity AS blocked
JOIN   LATERAL unnest(pg_blocking_pids(blocked.pid)) AS b(pid) ON true
JOIN   pg_stat_activity AS blocking ON blocking.pid = b.pid
WHERE  cardinality(pg_blocking_pids(blocked.pid)) > 0;

Locks that are still waiting

Every lock a backend has requested but not yet been granted.

SELECT l.pid,
       l.locktype,
       l.mode,
       l.granted,
       COALESCE(c.relname, l.transactionid::text) AS object
FROM   pg_locks l
LEFT   JOIN pg_class c ON c.oid = l.relation
WHERE  NOT l.granted
ORDER  BY l.pid;

Reproduce & verify

A real, single-session PostgreSQL reproduction

A literal transcript of SQL run against a live PostgreSQL instance in an isolated lab — the commands below are exactly what was executed.

1Write a TIMESTAMP WITH TIME ZONE literal with an explicit offset beyond the allowed range, such as +16:00.
2PostgreSQL parses the literal and validates the time-zone displacement.
3An out-of-range offset aborts the statement with SQLSTATE 22009.

A feed supplied timestamps with a malformed offset (+16:00), and every affected row failed to cast to timestamptz.

Schema setup

-- The error is self-contained in one statement; no schema is required.
SELECT 'no schema needed' AS setup_note;

Supplying an out-of-range UTC offset

SELECT TIMESTAMP WITH TIME ZONE '2026-01-01 12:00:00+16:00';

The session continues normally

SELECT 'ok' AS session_after_error;

What PostgreSQL actually returned

Schema setup output

    setup_note    
------------------
 no schema needed
(1 row)

Supplying an out-of-range UTC offset output

ERROR:  time zone displacement out of range: "2026-01-01 12:00:00+16:00"
LINE 1: SELECT TIMESTAMP WITH TIME ZONE '2026-01-01 12:00:00+16:00';
                                        ^

The session continues normally output

 session_after_error 
---------------------
 ok
(1 row)

Related & next steps

Follow the thread

Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.

Verification

PG 18.4

Last verified: 2026-07-24 (isolated lab, PostgreSQL 18.4)
Reviewed by: Verified against PostgreSQL 18.4 in an isolated lab environment
Audit status: reviewed