You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Debezium, we need to explicitly control the flushing of the replication slot to maintain a consistent position when streaming changes. We also allow users to disable our automatic management of the LSN on the replication slot if they wish to manage this using a separate out-of-band process based on their needs.
The issue is that PR #2941 automatically flushes the LSN, and when users have disabled Debezium's automatic flushing, the expectation is that the LSN on the replication slot remains unchanged; however, after upgrading to 42.7.1 or 42.7.2, this is no longer the case with the automatic flushing behavior introduced.
We are unable to upgrade to the latest driver as a result.
I'd like to recommend that the PGReplicationStream have a method that allows this automatic flushing behavior to be toggled off so that we can safely upgrade the driver and retain expected user behavior.
The text was updated successfully, but these errors were encountered:
In Debezium, we need to explicitly control the flushing of the replication slot to maintain a consistent position when streaming changes. We also allow users to disable our automatic management of the LSN on the replication slot if they wish to manage this using a separate out-of-band process based on their needs.
The issue is that PR #2941 automatically flushes the LSN, and when users have disabled Debezium's automatic flushing, the expectation is that the LSN on the replication slot remains unchanged; however, after upgrading to 42.7.1 or 42.7.2, this is no longer the case with the automatic flushing behavior introduced.
We are unable to upgrade to the latest driver as a result.
I'd like to recommend that the PGReplicationStream have a method that allows this automatic flushing behavior to be toggled off so that we can safely upgrade the driver and retain expected user behavior.
The text was updated successfully, but these errors were encountered: