Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[source-postgres] CDC Not Working. Successful syncs with 0 records for incremental tables #50435

Closed
1 task
jimmc2 opened this issue Dec 28, 2024 · 2 comments
Closed
1 task

Comments

@jimmc2
Copy link

jimmc2 commented Dec 28, 2024

Connector Name

source-postgres

Connector Version

3.6.21

What step the error happened?

During the sync

Relevant information

We are getting successful syncs and no noticeable errors in our logs but our CDC Postgres -> snowflake jobs just began outputting no records with no discernible reason why. I've seen a few other Postgres CDC issues from other people within the last two weeks as well but they seem to have different logging output than we do.

This began on 2024-12-23. I can provide additional configuration details but don't really have logs with errors to provide as it appears that everything is working properly.

Relevant log output

Contribute

  • Yes, I want to contribute
@jimmc2
Copy link
Author

jimmc2 commented Dec 30, 2024

#49802

After setting the Invalid CDC position behavior (Advanced) field we began receiving the same error as the above issue and believe they are related so closing my issue.

@jimmc2 jimmc2 closed this as completed Dec 30, 2024
@christinecommm
Copy link

We hit the exact same error as the one described above on 2025-01-13.

We received the following support from Airbyte: "The reason your incremental syncs are not succeeding is because the Postgres Source Connector is timing out looking for the WAL resume position. The amount of time allowed for this search is set on the Connector Settings page as Initial Waiting Time in Seconds (Advanced)."

In our case, increasing the Initial Waiting Time in Seconds (Advanced) to 2400 resolved our issue. We also increase our WAL size to 1TB, but we're unclear if this was required for resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants