↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

SQLSTATE / CLASS 22 · DATA EXCEPTION

2203E

Read PG 18 manual ↗

too_many_json_object_members

SQLSTATE
2203E
Condition name
too_many_json_object_members
Class
Data Exception
Source macro
ERRCODE_TOO_MANY_JSON_OBJECT_MEMBERS
Evidence
Definition only
Analysis & operational context

English SQLSTATE atlas: authored explanations and source/runtime evidence are separate from the manual definitions. View source ↗

<h1>2203E</h1>

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

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.

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.

Source evidence

Evidence belongs to the frozen source and runtime versions listed here. It is not a runtime verification of the selected manual version.

2203E is too_many_json_object_members in SQLSTATE Class 22.

Method: Read fixed definition.

src.errcodes.18.6

No fixed PostgreSQL 18.6 emitting path was resolved for 2203E in the bounded scan.

Method: Retain definition without inventing emitter.

Limits: Bounded scan does not prove no extension or historical path exists.

src.errcodes.18.6

The locked catalogue records 2203E from 12.0 without proving exact implementation introduction.

Method: Use catalogue boundary.

src.errcodes.18.6

Message templates

No extracted message template is attached to this condition.

Reproduction & repair cases

No reproduction case is attached to this condition.

Recorded runtime evidence

No runtime observation is attached to this entry.

Version history 1
  1. PG 11 → 12added

Definition snapshot: english-manuals:9afc70c604e02168c7f025b08b8… · English manual source