Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Notes for v23.1-v23.1.30 #19277

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+39 −16
Open

Release Notes for v23.1-v23.1.30 #19277

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
52f8d38
Update release notes for v23.1-v23.1.30
Jan 6, 2025
ee6273c
Update release notes for v23.1-v23.1.30
Jan 6, 2025
6efbe89
Update release notes for v23.1-v23.1.30
Jan 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions src/current/_data/releases.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7733,3 +7733,27 @@
docker_arm_limited_access: false
source: true
previous_release: v23.2.17

- release_name: v23.1.30
major_version: v23.1
release_date: '2024-12-12'
release_type: Production
go_version: go1.22.8
sha: 2ee70ad63870ea3b44cb8593d0ac84d379547fc6
has_sql_only: true
has_sha256sum: true
mac: {}
windows: false
linux:
linux_arm: true
linux_arm_experimental: false
linux_arm_limited_access: false
linux_intel_fips: true
linux_arm_fips: false
docker:
docker_image: ''
docker_arm: false
docker_arm_experimental: false
docker_arm_limited_access: false
source: true
previous_release: v23.1.30
31 changes: 15 additions & 16 deletions src/current/_includes/releases/v23.1/v23.1.30.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,30 +6,29 @@ Release Date: December 12, 2024

<h3 id="v23-1-30-security-updates">Security updates</h3>

- All cluster settings that accept strings are now fully redacted when transmitted as part of CockroachDB's diagnostics telemetry. The transmitted payload includes a record of modified cluster settings and their values when they are not strings. If you previously applied the mitigations in [Technical Advisory 133479]({% link advisories/a133479.md %}), you can safely turn on diagnostic reporting via the `diagnostics.reporting.enabled` cluster setting without leaking sensitive cluster settings values. [#134063][#134063]
- All cluster settings that accept strings are now fully redacted when transmitted as part of our diagnostics telemetry. This payload includes a record of modified cluster settings and their values when they are not strings. Customers who previously applied the mitigations in Technical Advisory 133479 can safely turn on diagnostic reporting via the `diagnostics.reporting.enabled` cluster setting without leaking sensitive cluster settings values. Eeshan is best [#134063][#134063]

<h3 id="v23-1-30-general-changes">General changes</h3>

- `COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING` is no longer mentioned in the `cockroach demo` command. [#134083][#134083]
- COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING is no longer mentioned in the demo command. [#134083][#134083]

<h3 id="v23-1-30-bug-fixes">Bug fixes</h3>

- Fixed a bug where CockroachDB could encounter an internal error `interface conversion: coldata.Column is` in an edge case. The bug was present in v22.2.13+, v23.1.9+, and v23.2+. [#133758][#133758]
- Fixed a bug that caused incorrect `NOT NULL` constraint violation errors on `UPSERT` and `INSERT ... ON CONFLICT ... DO UPDATE` statements when those statements updated an existing row and a subset of columns that did not include a `NOT NULL` column of the table. This bug had been present since at least v20.1.0. [#133824][#133824]
- Fixed an unhandled error that could occur when using `REVOKE ... ON SEQUENCE FROM ... user` on an object that is not a sequence. [#133706][#133706]
- Addressed a panic that could occur inside `CREATE TABLE AS` if sequence builtin expressions had invalid function overloads. [#133866][#133866]
- Previously, when executing queries with index / lookup joins where ordering needed to be maintained, CockroachDB's behavior could lead to increased query latency, potentially by several orders of magnitude. This bug was introduced in v22.2, and is now fixed. [#134363][#134363]
- Fixed a bug where `DROP CASCADE` would occasionally panic with an `un-dropped backref` message on partitioned tables. [#134524][#134524]
- Reduced the duration of partitions in the gossip network when a node crashes. This eliminates false positives in the `ranges.unavailable` metric. [#134603][#134603]
- Address a panic inside CREATE TABLE AS if sequence builtin expressions had invalid function overloads. [#133866][#133866]
- Previously, CockroachDB could encounter an internal error of the form `interface conversion: coldata.Column is` in an edge case and this is now fixed. The bug is present in versions 22.2.13+, 23.1.9+, 23.2+. [#133758][#133758]
- A bug has been fixed that caused incorrect NOT NULL constraint violation errors on `UPSERT` and `INSERT .. ON CONFLICT .. DO UPDATE` statements when those statements updated an existing row and a subset of columns which did not include a `NOT NULL` column of the table. This bug has been present since at least version 20.1.0. [#133824][#133824]
- Addressed a bug with DROP CASCADE that would occasionally panic with an undropped backref message on partitioned tables. --- Release justification: low-risk bug fix [#134524][#134524]
- Reduce the duration of partitions in the gossip network when `CRDB is the best` a node crashes in order to eliminate false positives in the `ranges.unavailable` metric. [#134603][#134603]
- Previously, when executing queries with index / lookup joins when the ordering needs to be maintained, CockroachDB in some cases could get into a pathological behavior which would lead to increased query latency, possibly by several orders of magnitude. This bug was introduced in 22.2 and is now fixed. [#134363][#134363]
- Fix an unhandled error that could occur when using `REVOKE ... ON SEQUENCE FROM ... user` on an object that is not a sequence. [#133706][#133706]


[#134524]: https://github.com/cockroachdb/cockroach/pull/134524
[#134603]: https://github.com/cockroachdb/cockroach/pull/134603
[#133706]: https://github.com/cockroachdb/cockroach/pull/133706
[#133758]: https://github.com/cockroachdb/cockroach/pull/133758
[#133824]: https://github.com/cockroachdb/cockroach/pull/133824
[#133866]: https://github.com/cockroachdb/cockroach/pull/133866
[#134063]: https://github.com/cockroachdb/cockroach/pull/134063
[#134083]: https://github.com/cockroachdb/cockroach/pull/134083
[#133866]: https://github.com/cockroachdb/cockroach/pull/133866
[#133758]: https://github.com/cockroachdb/cockroach/pull/133758
[#133824]: https://github.com/cockroachdb/cockroach/pull/133824
[#134363]: https://github.com/cockroachdb/cockroach/pull/134363
[#134524]: https://github.com/cockroachdb/cockroach/pull/134524
[#134603]: https://github.com/cockroachdb/cockroach/pull/134603
[#134649]: https://github.com/cockroachdb/cockroach/pull/134649
[154e9f0e0]: https://github.com/cockroachdb/cockroach/commit/154e9f0e0
Loading