modifying sql to do a join with the pg table after creating a temp table #146
Conversation
This file contains 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
DevanathanSabapathy1
requested review from
Brandon-Schur,
jiezhen-chen and
karle-nishi
karle-nishi
approved these changes
May 1, 2024
DevanathanSabapathy1
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
The issue is the query we currently have for getting replay stats uses pg tables and sys_views. The problem is having both these tables generates an execution plan that runs on Leader Node and the Compute Nodes. This causes a problem in Redshift and throws an error in some Redshift clusters
Description of changes:
To fix this issue, I removed the pg tables that are Leader Node only tables. This way we have an execution plan that runs only on the Compute nodes.
To verify that the new query generates a execution plan that does not involve Leader Node and Compute Node, I ran both the old query and the new query and verified that the new query does not have a LN step compared to the old query that will have an LN step in the execution plan.