Sync copied path building code with upstream - #10397
Open
svenklemm wants to merge 1 commit into
Open
Conversation
Two fixes to code copied from the planner. For plain tables we now consider TID scans first and stop early when one is required, which is needed for queries using WHERE CURRENT OF. For foreign tables we make sure the tuple estimate is never lower than the row estimate, which guards against an unknown reltuples value of -1.
|
@dbeck, @akuzm: please review this pull request.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Two fixes to code copied from the planner. For plain tables we now
consider TID scans first and stop early when one is required, which is
needed for queries using WHERE CURRENT OF. For foreign tables we make
sure the tuple estimate is never lower than the row estimate, which
guards against an unknown reltuples value of -1.