Release Noteslink
August 2023link
We now support the XML data type in PostgreSQL destinations.
In existing tables, the STRING data types for XML will remain unaffected. We will create new tables and columns using the XML data type when the source supports it.
June 2023link
We now support AWS PrivateLink for the following destinations:
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Aurora MySQL
- MariaDB MySQL
- MariaDB RDS MySQL
- MySQL
- MySQL RDS
- PostgreSQL
- SQL Server
- SQL Server RDS
We now support Azure Private Link for the following destinations:
September 2022link
In PostgreSQL destinations, we now drop the primary key constraints if the index row size exceeds the maximum index row size.
July 2021link
We have implemented a new format (V2) for consistency in the destination configuration information. This format is valid for the following destinations:
For more information, see our V2 config format documentation.
September 2020link
We have added a new test in the PostgreSQL destination setup form to verify CREATE TEMPORARY TABLES permissions. When you set up your PostgreSQL destination, you must grant the fivetran
user permission to create temporary tables in your PostgreSQL database. To learn how, see the setup guide for your PostgreSQL implementation:
June 2020link
We now replicate empty tables in a PostgreSQL source database as empty tables in the destination.
November 2019link
We now officially support Amazon Aurora PostgreSQL as one of our destinations.
Read our Amazon Aurora PostgreSQL documentation.
October 2018link
For the following destinations, Fivetran now drops the primary_key
field from existing tables in your destination if there is a primary_key
coming in from your data source:
- MySQL
- PostgreSQL
- SQL Server
- Redshift