2200B — escape_character_conflict
2200B
At a glance
2200B is escape_character_conflict. The fixed 18.6 call archive has no resolved native report group in this scan.
| Field | Value |
|---|---|
| SQLSTATE | 2200B |
| Condition | escape_character_conflict |
| Status | active |
| Known present by | 7.4 |
| Locked snapshots | 9.0.23, 9.1.24, 9.2.24, 9.3.25, 9.4.26, 9.5.25, 9.6.24, 10.23, 11.22, 12.22, 13.23, 14.24, 15.19, 16.15, 17.11, 18.6, 19beta3 |
| Macros | ERRCODE_ESCAPE_CHARACTER_CONFLICT |
| Aliases | — |
Meaning
2200B is escape_character_conflict. The fixed 18.6 call archive has no resolved native report group in this scan.
Messages
No fixed PostgreSQL primary, DETAIL, HINT, or severity was confirmed in the bounded source scan. This page is definition/scan-boundary reference only; runtime_verification remains not_run.
Diagnosis
Locate the pattern/escape parser or extension that selected the code and inspect its escape-character rules. A no-path scan is an evidence boundary, not an absence claim.
Response
Correct the actual pattern and escape configuration according to the deployed parser after locating the component that selected the code. Do not manufacture this SQLSTATE with a generic RAISE to stand in for parser behavior, and do not infer transaction recovery from this source-only boundary.
Versions
The locked catalogue records this condition from 7.4 in the listed formal snapshots and 19beta3; fixed source coverage is PostgreSQL 18.6.
Related
Sources
See the fixed source links and scope limits in the structured evidence record.