Skip to content

26.2.0 GA release notes#23205

Open
taroface wants to merge 32 commits intomainfrom
26.2-feature-highlights
Open

26.2.0 GA release notes#23205
taroface wants to merge 32 commits intomainfrom
26.2-feature-highlights

Conversation

@taroface
Copy link
Copy Markdown
Contributor

@taroface taroface commented Apr 21, 2026

Draft 26.2.0 GA release notes. Note:

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 21, 2026

Files changed:

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 21, 2026

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit 06aab42
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/69ec262ff6c59300089a721a

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 21, 2026

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit 06aab42
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/69ec262f782afa00081548f3

@github-actions
Copy link
Copy Markdown

Branch Existence Check: Failed

Found 6 issue(s) in versions.csv:

Context: EDUENG-614

  • ❌ v1.0: crdb_branch_name='release-1.0' does not exist in cockroachdb/generated-diagrams.
  • ❌ v1.1: crdb_branch_name='release-1.1' does not exist in cockroachdb/generated-diagrams.
  • ❌ v2.0: crdb_branch_name='release-2.0' does not exist in cockroachdb/generated-diagrams.
  • ❌ v2.1: crdb_branch_name='release-2.1' does not exist in cockroachdb/generated-diagrams.
  • ❌ v19.1: crdb_branch_name='release-19.1' does not exist in cockroachdb/generated-diagrams.
  • ❌ v19.2: crdb_branch_name='release-19.2' does not exist in cockroachdb/generated-diagrams.

@taroface taroface force-pushed the 26.2-feature-highlights branch from 9af70cd to e5330a2 Compare April 21, 2026 17:56
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 21, 2026

Deploy Preview for cockroachdb-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 9af70cd
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/69e7b9736424a70008491eb0

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 21, 2026

Deploy Preview for cockroachdb-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 06aab42
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/69ec262f6ffb060008db996f

@taroface taroface removed the request for review from kannanlakshmi April 21, 2026 21:21
@taroface taroface requested a review from rmloveland April 22, 2026 18:19
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Copy link
Copy Markdown
Contributor

@rmloveland rmloveland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, had some feedback but nothing blocking

<p class="feature-summary">Prevent auto-unlock of schema_locked tables</p>
<p class="feature-description">A new cluster setting <code>sql.schema.auto_unlock.enabled</code> controls whether DDL operations automatically unlock <code>schema_locked</code> tables. When set to <code>false</code>, DDL on schema-locked tables is blocked unless the user manually unlocks the table first. This allows customers using LDR to enforce <code>schema_locked</code> as a hard lock preventing user-initiated DDL. The default is <code>true</code>, preserving existing behavior.</p>
<p class="feature-summary">Schema lock enforcement</p>
<p class="feature-description">The cluster setting <code>sql.schema.auto_unlock.enabled</code> controls whether DDL operations automatically unlock <code>schema_locked</code> tables. When set to <code>false</code>, DDL statements on schema-locked tables are blocked unless manually unlocked. This allows users of Logical Data Replication (LDR) to enforce <code>schema_locked</code> as a hard lock preventing user-initiated DDL. The default is <code>true</code>.</p>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm not sure if it's worth adding this level of nuance in a feature highlight (cc @rafiss if you have opinions) - in the docs PR we made it clear that it can't always auto-unlock

suggest clarifying slightly with replacement text something like the following (IFF we care about this level of nuance, which i think we will, since it could lead to some user/support interactions re: "why doesn't this auto-unlock?"):

<p class="feature-description">The cluster setting <code>sql.schema.auto_unlock.enabled</code> controls whether DDL operations attempt to automatically unlock and re-lock <code>schema_locked</code> tables. When set to <code>false</code>, DDL statements on schema-locked tables are blocked unless manually unlocked. This allows users of Logical Data
  Replication (LDR) to enforce <code>schema_locked</code> as a hard lock preventing user-initiated DDL. Some schema changes still require manual unlock even when this setting is <code>true</code>. The default is <code>true</code>.</p>

Comment thread src/current/_includes/releases/v26.2/v26.2.0.md
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/upgrade-finalization.md Outdated
Comment thread src/current/_includes/releases/v26.2/upgrade-finalization.md Outdated
Copy link
Copy Markdown
Contributor

@jhlodin jhlodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested links and left a few comments, otherwise LGTM for my topic areas

Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Copy link
Copy Markdown
Contributor

@jhlodin jhlodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating my review with suggestions for Cloud content specifically

Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Copy link
Copy Markdown
Contributor

@jhlodin jhlodin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to remove 2DC active-passive which was bumped to Q2

Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/releases/cloud.md
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/_includes/releases/v26.2/v26.2.0.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/releases/cloud.md Outdated
Comment thread src/current/_includes/releases/v26.2/upgrade-finalization.md Outdated
Comment thread src/current/_includes/releases/v26.2/upgrade-finalization.md Outdated
Comment thread src/current/_includes/releases/v26.2/cluster-setting-changes.md Outdated
{% endcomment %}
- `ALTER TABLE ... DROP CONSTRAINT` can now be used to drop `UNIQUE` constraints. The backing `UNIQUE` index will also be dropped, as CockroachDB treats the constraint and index as the same thing. [#162345](https://github.com/cockroachdb/cockroach/pull/162345)

- Added the <a href="{% link v26.2/cluster-settings.md %}#setting-sql-stats-canary-fraction"><code>sql.stats.canary_fraction</code></a> cluster setting to enable <a href="{% link v26.2/canary-statistics.md %}">canary table statistics</a>. This setting controls the probability that table statistics will use canary mode (i.e., always use the freshest stats) instead of stable mode (i.e., use the second-freshest stats) for query planning `[0.0-1.0]`. [#167944](https://github.com/cockroachdb/cockroach/pull/167944)
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peachdawnleach Do you mind reviewing this and the following 2 items on canary stats? I learned that the entire feature is version-gated, so moved more release notes to this section and also reworded them a bit in the process.

@taroface taroface requested a review from jhlodin April 23, 2026 22:59
@taroface
Copy link
Copy Markdown
Contributor Author

Need to remove 2DC active-passive which was bumped to Q2

@jhlodin Done; PTAL!

@taroface taroface force-pushed the 26.2-feature-highlights branch from e50dea3 to e03bb66 Compare April 23, 2026 23:12
@taroface taroface force-pushed the 26.2-feature-highlights branch from dbfa1b4 to 5304f13 Compare April 24, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants