↑↓ select ↵ open ⌫ change scope Open full search

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

SQLSTATE / CLASS 22 · DATA EXCEPTION

2203D

Read PG 18 manual ↗

too_many_json_array_elements

SQLSTATE
2203D
Condition name
too_many_json_array_elements
Class
Data Exception
Source macro
ERRCODE_TOO_MANY_JSON_ARRAY_ELEMENTS
Evidence
Definition only
Analysis & operational context

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

<h1>2203D</h1>

At a glance

The locked condition names an excessive number of JSON array elements. No fixed PostgreSQL 18.6 emitting path was resolved in the bounded scan.

Meaning

The definition identifies too_many_json_array_elements, but the bounded PostgreSQL 18.6 source review did not resolve a native 2203D emitter. This page records the condition identity and cardinality boundary without assigning a JSON_TABLE/SQL/JSON wrapper, primary text, DETAIL, or HINT.

Diagnosis

Preserve the complete diagnostic and identify the actual emitting component and its element-count rule. Confirm from that operation whether it permits one item, multiple elements, or another documented cardinality; the condition name alone does not establish that a wrapper or aggregate exists or would repair it.

Response

After identifying the actual emitter, follow that component's documented element-count rule and correct the input or cardinality accordingly. Do not presume that a wrapper or aggregate 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#L228. The bounded source review did not resolve a native 2203D 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.

2203D is too_many_json_array_elements in SQLSTATE Class 22.

Method: Read fixed definition.

src.errcodes.18.6

No fixed PostgreSQL 18.6 emitting path was resolved for 2203D 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 2203D 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:1f5e01b462495af956b24f64bfc… · English manual source