Introduce colocate_allow_hash_schema option #29590
Open
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.
When running
yugabytedin development on local machines, we need to populate it with ~1500 tables.We found that
ysql_colocate_database_by_default=truesignificantly speeds up schema population.However, it doesn't allow primary keys with
HASHby design.All of our tables use
HASHpartitioning, and even though it doesn't make a lot of sense in development, we feel strongly that we want to let developersCREATE TABLEwith the same primary key as they'll use in production.This PR adds
colocate_allow_hash_schemaas an option, which is intended to be used withysql_colocate_database_by_default=trueto let you populate schema with HASH partitioned tables.