In our setup DMS pushes Parquet files on s3. Snowflake then loads data from there.
We’ve occasionally had to do a full table sync from scratch, which is painfully slow. We are going to have to do that in the very near future - when we are upgrading from Postgres 11 to Postgres 15.
The S3 step also seems unnecessarily complicated, since we have to expire data from the bucket.
How does PeerDB handle things like schema changes? Would the change replicate to Snowflake? (I’m sure this is in the docs, but I’m supposed to be on holiday this week ) Thanks for the quick reply.
Gotcha, that really helps. Schema changes feature is coming soon! We are actively working on it. This thread captures our thinking around it - https://news.ycombinator.com/item?id=36895220 Also have a good holiday! :)
In our setup DMS pushes Parquet files on s3. Snowflake then loads data from there.
We’ve occasionally had to do a full table sync from scratch, which is painfully slow. We are going to have to do that in the very near future - when we are upgrading from Postgres 11 to Postgres 15.
The S3 step also seems unnecessarily complicated, since we have to expire data from the bucket.
How does PeerDB handle things like schema changes? Would the change replicate to Snowflake? (I’m sure this is in the docs, but I’m supposed to be on holiday this week ) Thanks for the quick reply.