Fix bootstrapping ids for relating objects like indexes #777
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.
Description of Changes
The bootstrapping of system tables keeps the ids of related objects as
0
because is calledschema_for_table
that first consults the cache.Now, after the bootstrapping is done, re-read the data from the database to be sure the correct
ids
are assigned.API and ABI breaking changes
This is an internal break because the
system tables
schemas get0
for all the dependant objectsids
and now get the correct one.Expected complexity level and risk
1