2203E — too_many_json_object_members
The locked condition names an excessive number of JSON object members. No fixed PostgreSQL 18.6 emitting path 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
- too_many_json_object_members
- lang
- en
- sqlstate
- 2203E
Definition PG 18
2203E
At a glance {#at-a-glance}
The locked condition names an excessive number of JSON object members. No fixed PostgreSQL 18.6 emitting path was resolved in the bounded scan.
Meaning {#meaning}
The definition identifies too_many_json_object_members, but the bounded PostgreSQL 18.6 source review did not resolve a native 2203E emitter. This page records the condition identity and object-cardinality boundary without assigning a JSON_TABLE/SQL/JSON constructor, primary text, DETAIL, or HINT.
Diagnosis {#diagnosis}
Preserve the complete diagnostic and identify the actual emitting component and its object-member count rule. Confirm from that operation whether it permits the observed number of members or has another documented cardinality; the condition name alone does not establish that a wrapper or aggregate exists or would repair it. Do not infer a generic duplicate-key condition.
Response {#response}
After identifying the actual emitter, follow that component's documented object-member count rule and correct the input or cardinality accordingly. Do not presume that a wrapper or aggregation is available or that either would resolve this condition. If an ERROR occurred in an explicit transaction, roll back or roll back to the existing savepoint before retrying; autocommit can retry the corrected action.
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 errcodes.txt#L229. The bounded source review did not resolve a native 2203E emitting path; 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": "2203E is too_many_json_object_members in SQLSTATE Class 22."
}claims · bounded-source-scope
{
"claim_id": "bounded-source-scope",
"limits": "Bounded scan does not prove no extension or historical path exists.",
"method": "Retain definition without inventing emitter.",
"position": 1,
"runtime": [],
"sources": [
"src.errcodes.18.6"
],
"statement": "No fixed PostgreSQL 18.6 emitting path was resolved for 2203E 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 2203E 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#L229"
}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · english-manuals:a79491bce8cf846c7b679609417b1bcdd21ef3eb829e6d13033ea573f8c9b5b7
Text language: en · english-manuals:a79491bce8cf846c7b679609417b1bcdd21ef3eb829e6d13033ea573f8c9b5b7