[Snapshot] Invalid input syntax for type json with valid value

[eminano]

Describe the bug
A COPY error is received with a jsonb column value with the correct syntax. The value contains <i> which might need to be escaped in order to get it to work properly with the binary copy.

[dosubot]

The presence of <i> or other HTML-like tags inside a JSONB value should not cause a COPY error as long as the JSON syntax is valid and the value is properly quoted. PostgreSQL's jsonb type accepts any valid JSON string, including those with embedded HTML tags. Issues can arise if the value is not correctly serialized or escaped before being sent to PostgreSQL, especially when using binary COPY or certain drivers.

There is no evidence that <i> specifically needs to be escaped for jsonb columns during COPY operations. The error is more likely due to how the value is being encoded or transmitted—such as double-encoding, missing quotes, or incorrect escaping—rather than the presence of HTML-like content itself. Ensuring that the JSON is valid and properly quoted before COPY should resolve the issue. If you need a workaround, you can use a transformation to replace problematic JSONB values with a hardcoded valid value like {} to avoid errors during replication or processing, as discussed in this thread.

If you can share the exact value and COPY command, it may help pinpoint the root cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[eminano]

Could not reproduce.