It would be really convenient and more performant to correctly sync over Postgis geometry columns as their native geometry type, along with the indexing that was on the source postgres table.

In some cases the geometry column and indexing is necessary to even peform large spatial queries.

One way around it is to create a virtual column that handles this, hopefully that does not cause any issue with the fivetran transformations.