@kapa.ai How can I control Airbyte to treat

\u0000

as string in JSONB field rather than try to convert it to null bytes.. this is causing issue and failing pipeline...

Handling \u0000 (Null Bytes) in Postgres Destination This is a known issue with the Postgres destination connector. PostgreSQL does not support null bytes (

\u0000

) in text/JSONB fields, so the COPY operation fails when it encounters them. Current Behavior in the Connector The Postgres destination connector's

PostgresValueCoercer

already has logic to strip (not preserve) null bytes from string values before writing:

// PostgreSQL doesn't allow null bytes (\u0000) in text fields
// Replace them with empty string to prevent COPY errors
if (abValue.value.contains('\u0000')) {
    val sanitizedValue = abValue.value.replace("\u0000", "")
    value.abValue = StringValue(sanitizedValue)
}

[PostgresValueCoercer] This means the connector removes null bytes rather than treating them as a literal string — which is the only safe option given PostgreSQL's constraints. Why You're Still Seeing Failures There is an open GitHub issue (#75900) reporting that in some cases (e.g., MongoDB → Postgres syncs), the null byte sanitization is not applied correctly before the COPY operation, causing the pipeline to fail — and worse, sometimes reporting success even when data wasn't written. [GitHub Issue] Recommended Workarounds Since PostgreSQL fundamentally cannot store

\u0000

in text/JSONB fields, you cannot configure Airbyte to treat it as a literal string in JSONB — the database itself rejects it. Your options are: 1. Sanitize at the source — Remove or replace

\u0000

characters in your source data before syncing. This is the most reliable workaround mentioned in the issue. [GitHub Issue] 2. Upgrade your destination-postgres connector — Ensure you're on the latest version, as the null byte stripping logic (

PostgresValueCoercer

) should handle this automatically in recent versions. 3. Use Full Refresh → Overwrite mode — One forum user noted that

full_refresh → overwrite

worked while incremental/append-dedup failed, which may help as a temporary workaround. [Forum Post] 4. Monitor the open issue — The Airbyte team has escalated the false-success/COPY failure bug internally. You can track progress at GitHub issue #75900. > Note: There is no configuration option in Airbyte to preserve

\u0000

as a literal string in PostgreSQL JSONB — this is a PostgreSQL limitation, not an Airbyte configuration choice. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.