Incident brief
Invalid datetime format
A text value was cast to a date/time type, but PostgreSQL couldn't parse it as any recognized date/time format at all.
In 10 seconds
- What
- Invalid datetime format
- What triggers it
- Cast plain, unparseable text to date.
- The fix
- Send dates in ISO 8601 format (YYYY-MM-DD) — the manual's own recommended, unambiguous format.
- Proof
- Reproduced on PostgreSQL 16.14 → Casting plain garbage text to date was rejected with SQLSTATE 22007. The session was unaffected afterward.
The fix
What to do right now
The immediate, application-level response to this error.
- Send dates in ISO 8601 format (YYYY-MM-DD) — the manual's own recommended, unambiguous format.
- Validate the string is even shaped like a date in application code before sending it to PostgreSQL.
- Don't confuse this with 22008 — see the premium test for the difference between 'unreadable' and 'reads fine but doesn't exist'.
SELECT '1999-01-08'::date;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;Why it happens
What PostgreSQL is telling you
The mechanism behind the error, grounded in the official manual — not paraphrased.
PostgreSQL 16 Documentation — Date/Time Types, Table 8.10
1999-01-08 — ISO 8601; January 8 in any mode (recommended format)Read the full section on postgresql.org →
The unparseable cast
"not-a-real-date" doesn't match any date format PostgreSQL recognizes, per the manual's own list of accepted date inputs — so it's rejected before PostgreSQL can even ask whether the date itself makes sense.Confirming the session still works
The failed cast didn't affect the session — the next statement ran normally.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.
- 1Cast plain, unparseable text to date.
- 2PostgreSQL cannot recognize the text as any date format it knows.
- 3SQLSTATE 22007 is reported.
One client: cast a string PostgreSQL can't parse as any date format.
-- No table needed: the failure happens purely at the type-cast stage.
SELECT 'no schema required' AS setup_note;SELECT 'not-a-real-date'::date;SELECT 1 AS session_still_alive;What PostgreSQL actually returned
setup_note
--------------------
no schema required
(1 row)ERROR: invalid input syntax for type date: "not-a-real-date"
LINE 1: SELECT 'not-a-real-date'::date;
^ session_still_alive
----------------------
1
(1 row)22007 and 22008 sound similar but are different codes for different problems. This was tested directly: the same style of date cast, but with text that PostgreSQL CAN parse, on a day that doesn't exist on the calendar.
Cast '2024-02-30' (a well-formed-looking date string, but February has no 30th day) to date.
Without this
Above: text PostgreSQL can't parse at all is rejected with SQLSTATE 22007.
With this, tested
Below: text PostgreSQL CAN parse, but names a day that doesn't exist, is rejected with a DIFFERENT SQLSTATE — 22008.
What Pro unlocks here
- The exact prevention SQL — copy-paste ready
- Raw psql output captured from the Docker lab
- A senior-DBA action list to take it further
- Live monitoring queries to catch it in production
- The deeper audit: fix-that-fails counterexample, GUC before/after, server-log evidence
Related & next steps
Follow the thread
Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.
Related errors
Verification
- Last verified
- 2026-07-16 (Docker lab, PostgreSQL 16.14)
- Reviewed by
- Verified against PostgreSQL 16.14 in an isolated lab environment
- Audit status
- reviewed