SQLSTATE 2200TSeverity lowLab verified

Incident brief

Invalid XML processing instruction

xmlpi() rejects an illegal processing-instruction target; the name 'xml' (in any case) is reserved and cannot be used as a target.

Reproduced on PostgreSQL 18.4Verified 2026-07-24 (isolated lab, PostgreSQL 18.4)Reviewed by Verified against PostgreSQL 18.4 in an isolated lab environment

In 10 seconds

What: Invalid XML processing instruction
What triggers it: Call xmlpi(name xml, 'payload') using 'xml' as the processing-instruction target.
The fix: Use a non-reserved target name for the processing instruction.
Proof: Reproduced on PostgreSQL 18.4 → A single SELECT reproduces SQLSTATE 2200T; the reserved target 'xml' is rejected with a DETAIL saying so.

The fix

What to do right now

The immediate, application-level response to this error.

Use a non-reserved target name for the processing instruction.
Rename any 'xml'-prefixed target to an application-specific name.

Fix — SQL

-- The PI target name 'xml' is reserved; use another name.
SELECT xmlpi(name proc, 'payload');

Diagnose

See it live on the server

Run these against the affected instance to confirm the diagnosis before you act.

Standard triage — not specific to this error

These are canonical PostgreSQL system-catalog queries, shown as SQL to run. No sample output is attached because this is general triage, not a captured lab transcript.

This SQLSTATE does not have an error-specific live snapshot yet. These are the canonical system-catalog queries you run against the affected server to see the problem in real time — standard triage, not a reproduced transcript.

What is running right now

Active backends, how long each has been running, and what it is waiting on.

SELECT pid,
       state,
       wait_event_type,
       wait_event,
       now() - query_start AS running_for,
       left(query, 80)     AS query
FROM   pg_stat_activity
WHERE  state <> 'idle'
  AND  pid <> pg_backend_pid()
ORDER  BY running_for DESC NULLS LAST;

Who is blocking whom

Turn raw blocking PIDs into the actual queries on both sides of the wait.

SELECT blocked.pid    AS blocked_pid,
       blocked.query  AS blocked_query,
       blocking.pid   AS blocking_pid,
       blocking.query AS blocking_query
FROM   pg_stat_activity AS blocked
JOIN   LATERAL unnest(pg_blocking_pids(blocked.pid)) AS b(pid) ON true
JOIN   pg_stat_activity AS blocking ON blocking.pid = b.pid
WHERE  cardinality(pg_blocking_pids(blocked.pid)) > 0;

Locks that are still waiting

Every lock a backend has requested but not yet been granted.

SELECT l.pid,
       l.locktype,
       l.mode,
       l.granted,
       COALESCE(c.relname, l.transactionid::text) AS object
FROM   pg_locks l
LEFT   JOIN pg_class c ON c.oid = l.relation
WHERE  NOT l.granted
ORDER  BY l.pid;

Reproduce & verify

A real, single-session PostgreSQL reproduction

A literal transcript of SQL run against a live PostgreSQL instance in an isolated lab — the commands below are exactly what was executed.

1Call xmlpi(name xml, 'payload') using 'xml' as the processing-instruction target.
2PostgreSQL validates the processing-instruction target name.
3Because 'xml' is reserved, the statement aborts with SQLSTATE 2200T.

A generator emitted a processing instruction named 'xml' and every document failed to build.

Schema setup

-- The error is self-contained in one statement; no schema is required.
SELECT 'no schema needed' AS setup_note;

Using a reserved PI target name

SELECT xmlpi(name "xml", 'payload');

The session continues normally

SELECT 'ok' AS session_after_error;

What PostgreSQL actually returned

Schema setup output

    setup_note    
------------------
 no schema needed
(1 row)

Using a reserved PI target name output

ERROR:  invalid XML processing instruction
DETAIL:  XML processing instruction target name cannot be "xml".

The session continues normally output

 session_after_error 
---------------------
 ok
(1 row)

Related & next steps

Follow the thread

Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.

Verification

PG 18.4

Last verified: 2026-07-24 (isolated lab, PostgreSQL 18.4)
Reviewed by: Verified against PostgreSQL 18.4 in an isolated lab environment
Audit status: reviewed