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
126280: crosscluster/logical: use fresh internal session data r=yuzefovich a=yuzefovich
This commit switches usage of the current session's data in favor of a fresh internal session data when instantiating the executor and the txn used by the LWW row processor. I didn't quite tracked down why, but it appears that current session's data (which comes from the JobExecCtx) is inconsistent (in some cases I observed it to use Go defaults, perhaps because it was being mutated (?)), so using the fresh internal session data would alleviate that. (This is also exactly what would happen if we didn't use the WithSessionData option, but this way avoid an allocation on each executor usage). Microbenchmark show no difference (which is a good thing).
Epic: None
Release note: None
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments