Skip to content

Commit

Permalink
Rich's feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
kathancox committed Jan 8, 2025
1 parent dd72780 commit ee24a4a
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions src/current/_includes/releases/v24.2/v24.2.8.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,7 @@ Release Date: January 9, 2025
- `changefeed.kafka_throttling_hist_nanos` [#136603][#136603]
- Added support for multiple seed brokers in the new Kafka sink. [#136748][#136748]
- Added a new metric (`distsender.rangefeed.catchup_ranges_waiting_client_side`) that counts how many rangefeeds are waiting on the client-side limiter to start performing catchup scans. [#136835][#136835]

<h3 id="v24-2-8-{{-site.data.products.enterprise-}}-edition-changes">{{ site.data.products.enterprise }} edition changes</h3>

- Added changefeed support for the `mvcc_timestamp` option with the `avro` format. If both options are specified, the Avro schema includes an `mvcc_timestamp` metadata field and emits the row's mvcc timestamp with the row data. [#136016][#136016]
- Added changefeed support for the `mvcc_timestamp` option with the `avro` format. If both options are specified, the Avro schema includes an `mvcc_timestamp` metadata field and emits the row's MVCC timestamp with the row data. [#136016][#136016]
- Added a no-op `AWS_USE_PATH_STYLE` parameter for forward compatibility with v24.3. [#137025][#137025]

<h3 id="v24-2-8-sql-language-changes">SQL language changes</h3>
Expand All @@ -40,10 +37,10 @@ Release Date: January 9, 2025
- The `idle_in_session_timeout` setting now excludes the time spent waiting for schema changer jobs to complete, preventing unintended session termination during schema change operations. [#136502][#136502]
- Fixed a bug that causes the optimizer to use stale table statistics after altering an `ENUM` type used in the table. [#136759][#136759]
- Table statistics collection in CockroachDB could previously run into `no bytes in account to release` errors in some edge cases (when the SQL memory budget, configured via `--max-sql-memory` flag, was close to being exhausted). The bug has been present since v21.2 and is now fixed. [#136165][#136165]
- CockroachDB now better respects `statement_timeout` limit on queries involving the top K sort and merge join operations. [#136652][#136652]
- CockroachDB now better respects the `statement_timeout` limit on queries involving the top K sort and merge join operations. [#136652][#136652]
- Fixed an issue where license enforcement was not consistently disabled for single-node clusters started with `cockroach start-single-node`. The fix ensures proper behavior on cluster restarts. [#137011][#137011]
- Fixed a bug that caused queries against tables with user-defined types to sometimes fail with errors after restoring those tables. [#137354][#137354]
- Fixed a bug that causes an incorrect filesystem to be logged as part of the store information. [#137113][#137113]
- Fixed a bug that caused an incorrect filesystem to be logged as part of the store information. [#137113][#137113]
- Fixed a bug that has existed since v24.1 that would cause a set-returning UDF with `OUT` parameters to return a single row. [#137377][#137377]
- Fixed a bug that could cause an internal error if a table with an implicit (`rowid`) primary key was locked from within a subquery, like: `SELECT * FROM (SELECT * FROM foo WHERE x = 2) FOR UPDATE;`. The error could occur either under read-committed isolation, or with `optimizer_use_lock_op_for_serializable` enabled. [#137129][#137129]
- Fixed an issue where adding an existing column with the `IF NOT EXISTS` option could exit too early, skipping necessary handling of the abstract syntax tree (AST). This could lead to failure of the `ALTER` statement. [#137676][#137676]
Expand Down

0 comments on commit ee24a4a

Please sign in to comment.