Pain point · Reliability & bugs · Causes churn
A null byte causes the event persister to drop an entire batch
Part of the theme “Event persister stops reliably processing events after errors” · 2 reports · see them all
1 source thread · first seen 2026-09
Summary
On PostgreSQL, one event containing a null byte makes the persister repeatedly fail and discard every event in the batch. The messages are already acknowledged, so they are not redelivered and the emitting client receives no error.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“one event with a null byte (`\x00`) in its name, a resource label, or a payload string makes the event persister drop every event flushed”