Trigger-Derived Vector Columns Cause Sync Failures

Issue

A user-defined, trigger-generated vector column was added to a destination table, causing the sync to fail.

Environment

Destination: PostgreSQL

Resolution

To resolve this issue, use one of the following approaches instead of modifying Fivetran-managed tables:

Create a separate table for trigger-generated or derived data.
Create a view that references the source table and adds any computed fields.
If needed, contact our support team for help identifying a safe schema design.

In some cases, setting up the table and schema before starting the initial sync can resolve this issue. However, this may not fix problems caused by unsupported data types.

Cause

We aim to create a one-to-one replication of your source data in the destination. When you introduce changes to the destination tables, such as adding user-defined columns with unsupported data types, it may disrupt the sync process. We don't support excluding columns from syncs, and unsupported data types can lead to sync failures.