Skip to main content

Community

Connector Improvement: Postgres Connector: Flush WAL even when no relevant changes

Completed

Please sign in to leave a comment.

Comments

3 comments

  • Official comment

    Hi Sam,

    Thanks for your question here! I will share this feedback with our engineering team.

    Have you had a chance to review the new beta feature for Postgres called pgoutput Publications? https://fivetran.com/docs/databases/postgresql#logicalreplication

    This feature allows you to configure a Publication for your slot that only tracks changes for tables you have selected. That way, your slot won't fill up with transactions from other tables and instead will only include transactions from tables you are syncing with Fivetran. Would this alleviate the pain point you are currently facing? Please let me know!

    Hi Kevin,

    Sorry for the very late reply. This does sound ideal for us. We've had a very busy few months and the dummy insert cron job has been serving as a workaround for now.

    As soon as I get time I will try pgoutput.

    Thanks

    As an update, we have now launched the pgoutput update method to General Availability! Please let me know if you have any questions about this feature, more information is available in our docs here: https://fivetran.com/docs/databases/postgresql#logicalreplication

Didn’t find what you need?

Contact support