Investigating issue #2211: Bad query plans involving records #2222
Unanswered
langston-barrett
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
#2211 is a big issue for us at Galois at the moment - we're currently unable to produce satisfactory query plans for the most expensive rule in our analysis. Does anyone (@b-scholz, perhaps?) have any pointers on where we could start looking to fix this? We were thinking these choices probably get made somewhere inside of
ast2ram/seminaive, perhaps somewhere inside ofClauseTranslator::translateRecursiveClause?Much appreciated in advance!
Beta Was this translation helpful? Give feedback.
All reactions