Hi again... I´m trying to figure out the table sizes in the destination. In my Postgres source, I have a table with 80k size. I´m using incremental + history deduped sync and in my redshift destination, the table size is 4G. I created a new table in destination, just without the Airbyte columns, and the table dropped to 10M. Should the size in the destination be SSSOOO high? Is there a way to config it differently?

I would skip the view and create it manually in redshift instead... it looks like it's currently importing the view as a table so all the data goes in it.

I just wanted to avoid to load the source tables to redshift..

Hello laila ribke, it's been a while without an update from us. Are you still having problems or did you find a solution?

Hi, we particularly, after evaluating all options and having in mind that our priority is to be cost effective, staged to redshift with S3 and then transform data with dbt and load the warehouse