ADBDEV-8931: Avoid using gp_tablespace_segment_location in a correlated subplan#2137
Closed
ADBDEV-8931: Avoid using gp_tablespace_segment_location in a correlated subplan#2137
Conversation
RekGRpth
changed the title
RekGRpth
changed the title
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.
Avoid using gp_tablespace_segment_location in a correlated subplan
The gp_tablespace_segment_location function is marked as being executed on all
segments. When used in a correlated subplan, when its argument depends on the
outer plan, it may produce incorrect results. We plan to disable such plans.
Rewrite arenadata_toolkit to avoid using the correlated function on segments in
the subplan.
Ticket: ADBDEV-8931