-
Notifications
You must be signed in to change notification settings - Fork 4.1k
workload/schemachange: support user-defined schemas #54408
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Description
Is your feature request related to a problem? Please describe.
The random schemachange workload is a powerful tool to catch bugs and ensure that we properly classify errors. In the 20.2 release we added support for user-defined schemas. It will be very valuable to exercise the interactions between schemas and all of the other schema changes.
Describe the solution you'd like
In order to support user-defined schemas, there's going to be multiple steps. We should take it one step at a time.
- Add a
createSchemaop - Add a
dropSchemaop - probably withCASCADE - For each of the objects which can exist in a schema, start to namespace them by schema with some chance of picking the public schema
- tables
- enums
- views
With this above task we'll also need to change all of the code that discovers these various objects.
The first two steps should be reasonably trivial. Step 3 is where things get a bit trickier.
Additional context
For an example PR that adds a new concept to the tool you can refer to #54351. j
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.