[DBZ-PGYB][yugabyte/yugabyte-db#25716] Set GUC to disable catalog version check for connections #169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Recent changes in YugabyteDB introduced some changes where the
relcache/catcache
is reloaded as soon asyb_read_time
is set. Now that caused an issue with the snapshots in the connector i.e. whenever the connector sets theyb_read_time
and goes on to take the snapshot by running aSELECT *
query, it gets the following error:Solution
As a workaround, we will now bypass the catalog version check by setting a GUC
yb_disable_catalog_version_check
at the connection level so that we do not hit the error during snapshot.Note that we do not require this during streaming phase and since streaming used a separate object of
ReplicationConnection
class, we will not be modifying it.This closes yugabyte/yugabyte-db#25716