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
150270: bazelbuilder: add `s390x` support r=rail a=rickystewart
The `s390x` version of the image has the build utilities installed,
but NOT some unnecessary bits like the cloud CLI's.
Epic: CRDB-21133
Part of: DEVINF-1495
150281: kvcoord: disallow pipelining while write buffering is enabled r=miraradeva,arulajmani a=stevendanna
The interaction between pipelining and write buffering has revealed a couple of subtle bugs. Further, these two optimisations are largely overlapping. In the happy case, when write buffering is enabled, we expect almost not write pipelining.
Here, we disable pipelining when write buffering is enabled.
The upside of this is:
1. It avoids other possible bugs in the interaction between these features.
2. It makes it a bit easier to reason about the behaviour of write-buffered transactions.
The downsides include:
1. This results in a negative performance impact for users who turn on write buffering but whose transactions often result in buffering later being disabled. (Mitigated by the second commit).
2. Write pipelining has been the default for many releases and it is not clear that running with write pipelining disabled is as well tested as the enabled code path.
Fixes#149911
Epic: none
Release note: None
150283: changefeedccl: fix ALTER CHANGEFEED max PTS age bug r=KeithCh,asg0451 a=andyyang890
This patch fixes a bug where modifying a changefeed with ALTER CHANGEFEED
that either unset or left the `gc_protect_expires_after` option unset would
cause the changefeed's max PTS age to become unbounded instead of being set to
the default value configured by the `changefeed.protect_timestamp.max_age`
cluster setting.
This bug was occurring because the ALTER CHANGEFEED code was manually querying
the option instead of relying on the CREATE CHANGEFEED code path that also
consulted the cluster setting. This inconsistency has now been corrected.
Fixes#148029
Release note (bug fix): A bug where modifying a changefeed with ALTER CHANGEFEED
that either unset or left the `gc_protect_expires_after` option unset would
cause the changefeed's max PTS age to become unbounded instead of being set to
the default value configured by the `changefeed.protect_timestamp.max_age`
cluster setting.
Co-authored-by: Ricky Stewart <[email protected]>
Co-authored-by: Steven Danna <[email protected]>
Co-authored-by: Andy Yang <[email protected]>
0 commit comments