sql: cap the tenant IDs that can be allocated via create_tenant #101928
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.
Requested by @yuzefovich here.
This patch introduces a limit (MaxUint32) to the fixed IDs that can be
selected by
crdb_internal.create_tenant
. This ensures that there arealways IDs remaining available for CREATE TENANT after the maximum
value has been selected via
create_tenant
.Release note: None
Epic: CRDB-23559