-
Notifications
You must be signed in to change notification settings - Fork 1k
Use ECs and joininfo when checking the need for Ordered Append #8994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
At the moment we go over the parse tree to collect these clauses independently. This seems excessive, because during the hypertable expansion all this data is already prepared by the Postgres planner.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8994 +/- ##
==========================================
+ Coverage 82.53% 82.59% +0.05%
==========================================
Files 249 249
Lines 48510 48544 +34
Branches 12388 12393 +5
==========================================
+ Hits 40040 40096 +56
- Misses 3510 3539 +29
+ Partials 4960 4909 -51 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@erimatnor, @fabriziomello: please review this pull request.
|
| -> Materialize (actual rows=10.00 loops=1) | ||
| -> Merge Append (actual rows=3.00 loops=1) | ||
| Sort Key: m3."time" | ||
| -> Custom Scan (ChunkAppend) on metrics_space m3 (actual rows=3.00 loops=1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the old check failed in some cases, so now we're getting more efficient plans.
At the moment we go over the parse tree to collect these clauses independently. This seems excessive, because during the hypertable expansion all this data is already prepared by the Postgres planner.
Related to #8987 and #8706
Disable-check: force-changelog-file