Possible performance issue with router planner relation renaming
Open
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
UpdateRelationNames() uses 0(n) lookup to find relation restriction for current relation. This could cause performance issues when there are many relations in the query.
This lookup could possibly be replaced with a hash search.
Contributor guide
Assessment
This issue has not been assessed yet.