2203E — too_many_json_object_members
2203E
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.
| Field | Value |
|---|---|
| SQLSTATE | 2203E |
| Condition | too_many_json_object_members |
| Status | active |
| Known present by | 12.0 |
| Locked snapshots | 12.22, 13.23, 14.24, 15.19, 16.15, 17.11, 18.6, 19beta3 |
| Macros | ERRCODE_TOO_MANY_JSON_OBJECT_MEMBERS |
| Aliases | — |
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
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
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
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
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.