22032 — invalid_json_text
JSON text is invalid for the consuming operation. No fixed 18.6 emitting report group was resolved in the bounded scan.
English manual coverage begins with PostgreSQL 8.1. Source history and runtime observations have their own recorded version boundaries.
Reading PG 18·Select a recorded version
- aliases
- Unknown
- class name
- Data Exception
- condition name
- invalid_json_text
- lang
- en
- sqlstate
- 22032
Definition PG 18
22032
At a glance {#at-a-glance}
JSON text is invalid for the consuming operation. No fixed 18.6 emitting report group was resolved in the bounded scan.
Meaning {#meaning}
The locked definition names invalid_json_text, but the bounded PostgreSQL 18.6 source review did not resolve a native emitting report group for this code. This page therefore does not assign a parser function, primary text, DETAIL, HINT, severity path, or SQL/JSON mode from the condition name alone.
Diagnosis {#diagnosis}
If 22032 appears, preserve the complete diagnostic and the consuming operation, including whether the input was json, jsonb, SQL/JSON, or an extension value. Validate the exact text and encoding at that boundary, but do not replace the unknown emitter with a guessed ordinary cast or client path. Related JSON cardinality codes have their own fixed guards.
Response {#response}
Use the actual emitter’s primary, DETAIL, and HINT to repair the JSON text or its boundary. If the operation is in an explicit transaction and raises ERROR, roll back or roll back to the existing savepoint before retrying; autocommit can retry corrected input. This recovery guidance is general and is not a 22032 runtime observation.
Versions {#versions}
The locked catalogue records this condition from 12.0. Only the PostgreSQL 18.6 definition row is fixed here; no native emitting path or natural runtime observation is claimed.
Related {#related}
Sources {#sources}
The fixed definition row is src/backend/utils/errcodes.txt#L217. The bounded source review did not resolve a native 22032 emitter; the structured evidence record keeps that unknown scope explicit, and no natural runtime was run.
Compare versions
SQLSTATE evidence and recorded runtime versions
claims · identity
{
"claim_id": "identity",
"limits": "",
"method": "Read fixed definition.",
"position": 0,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "22032 is invalid_json_text in SQLSTATE Class 22."
}claims · bounded-source-scope
{
"claim_id": "bounded-source-scope",
"limits": "A bounded scan does not prove no extension or historical path exists.",
"method": "Retain definition evidence without inventing an emitter.",
"position": 1,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "No fixed PostgreSQL 18.6 emitting path was resolved for 22032 in the bounded scan."
}claims · history
{
"claim_id": "history",
"limits": "",
"method": "Use catalogue boundary.",
"position": 2,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "The locked catalogue records 22032 from 12.0 without proving exact implementation introduction."
}sources · src.errcodes.18.6
{
"commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
"docs_url": "",
"kind": "upstream_source",
"location": "",
"path": "src/backend/utils/errcodes.txt",
"position": 0,
"sha256": "6e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba",
"source_id": "src.errcodes.18.6",
"tag": "REL_18_6",
"url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt#L217"
}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · english-manuals:9bb41870341f300d07d135e374ae7358ee3661b3caba0cd99fb2c130b997b502
Text language: en · english-manuals:9bb41870341f300d07d135e374ae7358ee3661b3caba0cd99fb2c130b997b502