You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
perf: reference prior CTE data via unnest when evaluating later CTE - #2024
When we send CTE subselects to be evaluated separately from the top-level query, sometimes the subselects reference earlier executed CTEs (e.g., CTE b references CTE a). When we send CTE b, we need to include the values that CTE a previously returned; this is done via re-writing the CTE b subselect to include a WITH clause with CTE a's returned values, so that when we execute it separately from the top-level query, it has everything it needs to return the values it should. Right now, this is done with a VALUES clause with all the DataRows inlined as tuples. Example,
WITH a (id, status) AS (VALUES (1::bigint, 'VIP'::text), (2, 'regular')) SELECT x.id, y.id FROM a x JOIN a y ON x.status = y.status
This migrates those from VALUES to unnest (via Bind param array) for massive speedup (follow up to #2003, #2023).
Compared 56c21c2 with e084496 on c7i.metal-48xl (on-demand).
This branch has not been deployed
No deployments
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
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.
When we send CTE subselects to be evaluated separately from the top-level query, sometimes the subselects reference earlier executed CTEs (e.g., CTE b references CTE a). When we send CTE b, we need to include the values that CTE a previously returned; this is done via re-writing the CTE b subselect to include a WITH clause with CTE a's returned values, so that when we execute it separately from the top-level query, it has everything it needs to return the values it should. Right now, this is done with a VALUES clause with all the DataRows inlined as tuples. Example,
This migrates those from VALUES to unnest (via Bind param array) for massive speedup (follow up to #2003, #2023).