Reduce "extract" cardinality with DISTINCT select #3203
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.
We've been experiencing very bad PostreSQL performances lately, related to facts <-> node queries such as:
With correspdonding
EXPLAIN ANALYZE
plan:By replacing all
SELECT r1.*
clauses bySELECT DISTINCT r1.*
, I have been able to significantly improve performances - almost two orders of magnitude - as shown by correspondingEXPLAIN ANALYZE
:I have tracked this to the
compile-extract
function, which I believe would benefit from the following single-liner PR.Does it make sense ?