Move schema max object to 'backwards-incompatible' #21016
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the v25.4.0 release notes, `sql.schema.approx_max_object_count` was already listed under 'Key cluster settings changes', but as discussed on DOC-14949 this is a backwards-incompatible change, since it will prevent users of large clusters from creating schema objects after the upgrade until they modify this setting. Moving it to the 'Backwards-incompatible changes' section for higher visibility to lower the chance of an unpleasant surprise for users during upgrade. Addresses DOC-14949
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
Files changed:
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
Contributor
Author
|
@rafiss this docs PR moves the max schema objects cluster setting into the 'Backwards incompatible changes' section of v25.4.0 release notes to make it more visible to users and avoid unpleasant surprise after upgrade for large cluster operators (it was already in the list of cluster settings changes in the release notes but it's not as visible there) cc @mwang1026 FYI |
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
rafiss
approved these changes
Nov 6, 2025
…rds-incompatible-change
rmloveland
deleted the
20251106-DOC-14949-max-schema-objects-backwards-incompatible-change
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the v25.4.0 release notes,
sql.schema.approx_max_object_countwas already listed under 'Key cluster settings changes', but as discussed on DOC-14949 this is a backwards-incompatible change, since it will prevent users of large clusters from creating schema objects after the upgrade until they modify this setting.Moving it to the 'Backwards-incompatible changes' section for higher visibility to lower the chance of an unpleasant surprise for users during upgrade.
Addresses DOC-14949