Incident brief
Invalid XML document (DOCUMENT)
XMLPARSE(DOCUMENT ...) requires well-formed XML; mismatched opening and closing tags raise this data exception with a DETAIL pointing at the mismatch.
In 10 seconds
- What
- Invalid XML document (DOCUMENT)
- What triggers it
- Call XMLPARSE(DOCUMENT '<...>') with content whose tags do not match.
- The fix
- Correct the markup so every opening tag has a matching closing tag.
- Proof
- Reproduced on PostgreSQL 18.4 → A single SELECT reproduces SQLSTATE 2200M; the mismatched tags are rejected and the DETAIL names them.
The fix
What to do right now
The immediate, application-level response to this error.
- Correct the markup so every opening tag has a matching closing tag.
- Validate or generate XML with a real serializer rather than string concatenation.
-- Parse only well-formed XML.
SELECT XMLPARSE(DOCUMENT '<order></order>');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;Why it happens
What PostgreSQL is telling you
The mechanism behind the error, grounded in the official manual — not paraphrased.
PostgreSQL 18 Documentation — Appendix A. PostgreSQL Error Codes (Table A.1, Class 22 — Data Exception)
2200M → invalid_xml_documentRead the full section on postgresql.org →
Parsing a malformed XML document
The opening <order> tag is closed with </total>, so libxml reports 'Opening and ending tag mismatch' and PostgreSQL raises 'invalid XML document'.The session continues normally
The failing statement ran outside a transaction block, so nothing was left in a bad state — the next statement in the same connection runs normally.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 XMLPARSE(DOCUMENT '<...>') with content whose tags do not match.
- 2PostgreSQL (via libxml) validates that the document is well-formed.
- 3The tag mismatch aborts the statement with SQLSTATE 2200M and a DETAIL naming the tags.
A feed built XML by hand and a stray closing tag made the whole document fail to parse.
-- The error is self-contained in one statement; no schema is required.
SELECT 'no schema needed' AS setup_note;SELECT XMLPARSE(DOCUMENT '<order></total>');SELECT 'ok' AS session_after_error;What PostgreSQL actually returned
setup_note
------------------
no schema needed
(1 row)ERROR: invalid XML document
DETAIL: line 1: Opening and ending tag mismatch: order line 1 and total
<order></total>
^ session_after_error
---------------------
ok
(1 row)The same XMLPARSE succeeds once the tags match.
We reparse a well-formed document to show it is accepted.
Without this
Before: mismatched tags abort the parse
With this, tested
After: matching tags parse cleanly
What Pro unlocks here
- The exact prevention SQL — copy-paste ready
- Raw psql output captured from the Docker lab
- A senior-DBA action list to take it further
- Live monitoring queries to catch it in production
- The deeper audit: fix-that-fails counterexample, GUC before/after, server-log evidence
Related & next steps
Follow the thread
Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.
Verification
- 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