Add a step to analyze partitioned parent tables. - #117
Open
mvnural wants to merge 2 commits into
Open
Conversation
We need to do this after all orgSpecific partitioned webready tables are populated so we don't have to worry about it after cloning. We do have individual child partitions analyzed as part of the workflow but the root partitions are not automatically analyzed. This means the planner will be completely blind when we don't do partition pruning and as a result will chose wildly inefficient query plans in such cases.
Child-partitions are already analyzed immediately after they are created so no need to re-analyze them at this point. We only want the parent partition. This should cut down the time for this step significantly.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We need to do this after all orgSpecific partitioned webready tables are populated so we don't have to worry about it after cloning. We do have individual child partitions analyzed as part of the workflow but the root partitions are not automatically analyzed. This means the planner will be completely blind when we don't do partition pruning and as a result will chose wildly inefficient query plans in such cases.