[DOC-7783] Release notes for v23.2.0-alpha.2 #17929
Conversation
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
mdlinville
force-pushed
the
v23.2.0-alpha.2-release-notes
branch
2 times, most recently
from
eeef0c5 to
72b1e2d
Compare
|
|
||
| [#110606][#110606] | ||
|
|
||
| - Added a check to disallow queries that use predicate locking, since explicit uniqueness checks are not yet supported under Read Committed isolation. `INSERT`, `UPDATE`, and `UPSERT` statements against some `REGIONAL BY ROW` tables will fail under Read Committed isolation with the following error: |
There was a problem hiding this comment.
@michae2 PTAL and make sure I've got this right.
| @@ -34,28 +58,49 @@ Release Date: October 2, 2023 | |||
| - A synthetic `dropped` column have been added to the `pg_attribute` table. This column tracks the attribution numbers for dropped attributions, to work around issues with ORMs that are not designed to handle gaps in attribution numbering in the `pg_attribute` table. [#111019][#111019] | |||
| - Fixed a rare internal error in the `unnest` and `information_schema._pg_expandarray` [built-in functions](https://www.cockroachlabs.com/docs/v23.2/functions-and-operators) where passed string arguments could be cast to an array. [#110956][#110956] | |||
| - External connection URLs now accept the scheme `azure-blob` for connections to Azure Blob Storage and the scheme `azure-kms` for connections to Azure KMS. For backward compatibility, schemes `azure` and `azure-storage` schemes continue to work for connections to Azure Blob Storage. [#111217][#111217] | |||
| - Fixed a bug where vectorized `COPY FROM` could produce a plan with more than one RenderNodes, when only zero or one should be allowed. This could result in multiple render nodes in a table with a hash shareded primary key. [#111284][#111284] | |||
There was a problem hiding this comment.
@cucaroach PTAL and make sure I've got this right.
| @@ -34,28 +58,49 @@ Release Date: October 2, 2023 | |||
| - A synthetic `dropped` column have been added to the `pg_attribute` table. This column tracks the attribution numbers for dropped attributions, to work around issues with ORMs that are not designed to handle gaps in attribution numbering in the `pg_attribute` table. [#111019][#111019] | |||
| - Fixed a rare internal error in the `unnest` and `information_schema._pg_expandarray` [built-in functions](https://www.cockroachlabs.com/docs/v23.2/functions-and-operators) where passed string arguments could be cast to an array. [#110956][#110956] | |||
| - External connection URLs now accept the scheme `azure-blob` for connections to Azure Blob Storage and the scheme `azure-kms` for connections to Azure KMS. For backward compatibility, schemes `azure` and `azure-storage` schemes continue to work for connections to Azure Blob Storage. [#111217][#111217] | |||
| - Fixed a bug where vectorized `COPY FROM` could produce a plan with more than one RenderNodes, when only zero or one should be allowed. This could result in multiple render nodes in a table with a hash shareded primary key. [#111284][#111284] | |||
| - Fixed a bug in DB Console's Statement Diagnostic page that could cause the page to crash if the response was larger than 50 KB. The page now keeps pulling results until no maximum size errors are encountered. [#111128][#111128] | |||
There was a problem hiding this comment.
@j82w PTAL and make sure I've got this right.
|
|
||
| <h3 id="v23-2-0-alpha-2-contributors">Contributors</h3> | ||
|
|
||
| This release includes 102 merged PRs by 43 authors. | ||
| This release includes [157 merged PRs by 54 authors](https://github.com/cockroachdb/cockroach/compare/v23.2.0-alpha.1...2111b61b2d7c789bc03b1e9392062df80c779075). |
There was a problem hiding this comment.
@mikeCRL WDYT about linking to the Git comparison so the reader can see every commit if they want to? I'm not sure how to automate generating this link. I've asked Nick if we can take advantage of releases.yml somehow.
There was a problem hiding this comment.
Great idea. Raised an issue. I suspect that we may want to use the latest release's tag instead of its commit SHA as they're functionally equivalent, but the former is more meaningful to humans.
(cockroachdb/cockroach@v23.2.0-alpha.1...v23.2.0-alpha.2
over
cockroachdb/cockroach@v23.2.0-alpha.1...2111b61)
There was a problem hiding this comment.
We already include this in a different part of the release note, but we can think about how we wish to display it: https://www.cockroachlabs.com/docs/releases/v23.2#v23-2-0-alpha-2-changelog
This is technically commits and not PRs, so it might be odd to display PRs as the link title when we're really showing commits at the destination. Mike and I have agreed to table this for the time being.
There was a problem hiding this comment.
nPRs will always be smaller than nCommits. The compare link lets them see every commit that is in the release, not only those that come from PRs (not everything comes from a PR these days) and have release note text.
Generated notes for SHA 10d282dc9045ebb8b3faaf891706a13b08177949 before edits
Simultaneous copyedit. Also experiment with adding a Github comparison link
mdlinville
force-pushed
the
v23.2.0-alpha.2-release-notes
branch
from
72b1e2d to
1baa57a
Compare
mdlinville
force-pushed
the
v23.2.0-alpha.2-release-notes
branch
from
1baa57a to
6d586a2
Compare
[DOC-7783] Release notes for v23.2.0-alpha.2
Initial commit represents the generated notes for SHA
10d282dc9045ebb8b3faaf891706a13b08177949before editsLatest commit updates the hash to
2111b61b2d7c789bc03b1e9392062df80c779075with a copyedit for the new notes.Preview: releases/v23.2.md