Error with replication slot getting full and invalidated during initial sync from Supabase to Snowflake


When syncing data from Supabase (Postgres) to Snowflake, encountering issues with the replication slot getting full and invalidated during the initial sync process, leading to the need to drop and recreate the slot and perform a full sync repeatedly. Seeking advice on how to address this ongoing issue.


hey folks, I’m connecting from supabase (Postgres) to Snowflake, when performing the initial sync I keep having the error where the replication slot gets full and invalidated, meaning I have drop the slot and recreate it, then perform a full sync again, so I’m never able to complete the sync, since the replication slot eventually gets invalidated again.

any advice on how to proceed?

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["supabase", "postgres", "snowflake", "initial-sync", "replication-slot", "full-sync", "invalidated"]