Issue with Postgres Connector and User Defined Cursor


The user is experiencing an issue with the Postgres connector where the cursor moves even when the destination fails, causing missing data upon retry. They are seeking a solution for this problem.


Hi all,

I noticed something strange when using the postgres connector (using Scan Changes with User Defined Cursor)
When the destination failed the cursor will still move meaning that when it will retry, it won’t load the entire missing data

Did anyone encounter that and has a solution?

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

["postgres-connector", "user-defined-cursor", "destination-failure", "missing-data", "retry"]