Destination Improvement: UUID type unsupported in Postgres destination
PlannedCreating this Feature Request on behalf of the customer.
Summary:
Reverse ETL currently does not support writing to columns of type UUID in PostgreSQL destinations. Syncs fail when UUID columns are present, forcing customers to use text-based alternatives.
Impact:
-
Prevents use of native UUID types, constraints, and indexing.
-
Causes schema mismatches and added maintenance overhead.
Customer Ask:
Enable Reverse ETL to write to UUID columns in PostgreSQL, handling automatic casting from text-based UUID values where applicable.
Business Justification:
UUIDs are a common standard for identifiers. Supporting them ensures correctness, referential integrity, and better performance for PostgreSQL users.
Priority:
High — impacts schema design and operational efficiency
-
Official comment
Hi Atishi,
Thanks for sharing your request. I've created a roadmap item for the feature and will investigate when/how we can implement it. I will be sharing any progress here.
In the meantime, could you please share which source connector(s) you use to write to Postgres?
Thanks,
Val Kulichenko, Fivetran Product Team
Please sign in to leave a comment.
Comments
1 comment