Connector Improvement: HVR should support custom rewin option on PostgreSQL DB in case of replication slot deletion by DB
AnsweredWhich connector?:
PostgreSQL DB as source
Additional details:
HVR should support custom rewin option on PostgreSQL DB in case of replication slot deletion by DB. We have a lot of use-cases almost wevery week where a replication slot gets dropped by Azure during maintenance and we end up doing full refreshes. This is not a viable option to perform a full refresh every time as some DBs are very large(TBs in size). It would be extremely helpful to have a custom rewind option for PostgreSQL SQL replication. HVR supports it for Oracle and other DBs but not PostgreSQL.
-
Hi Saurav,
Thank you for this feature request. We understand the impact of repeated full refreshes, especially for terabyte-sized databases.
We are evaluating a Capture Rewind capability for PostgreSQL logical replication in HVR, which could help avoid a full refresh when a replication slot is lost. We will update this request once we have more clarity on feasibility and next steps.
Best regards,
Edwin
Please sign in to leave a comment.
Comments
1 comment