-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[#18082] YSQL: Stop using ForeignScan for YB relations
Summary: Since implementation of aggregate pushdown for scan types other than ForeignScan, the ForeignScan and the YbSeqScan are functionally equivalent, so we switch to using the YbSeqScan, as it is more unified with IndexScan and IndexOnlyScan, which are also used to scan YB relation. Unification should make future developments easier. For consistency with previous design decision explain now shows "Seq Scan" if the plan node is a YbSeqScan node, hiding implementation details from the end user. Though YbSeqScan shows "Filter" and "Remote Filter" in different order, if both are present, so there are changes in the expected EXPLAIN output. The order of YbSeqScan filters consistent with the order of index scan and matches their evaluation order (remote filter goes first). There is no known way to force ForeignScan-based scan on Yugabyte tables. To help catch such cases, if any, the ForeignScan plan node on Yugabyte tables now shows "YB Foreign Scan" in the EXPLAIN output. Jira: DB-7124 Test Plan: Make sure existing regressions tests work. Modifications to expected output are needed due to differencies in EXPLAIN output. Reviewers: jason, telgersma Reviewed By: jason, telgersma Subscribers: ssong, yql Differential Revision: https://phorge.dev.yugabyte.com/D27297
- Loading branch information
1 parent
67aba99
commit 465ee2c
Showing
27 changed files
with
336 additions
and
391 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.