Closed Gurmokh closed 1 year ago
I believe this recent commit addresses the issue, and this can be marked as resolved.
https://github.com/ossc-db/pg_hint_plan/commit/a3646e1b073cb51c6a9aa0b5af898e4342c330d5
If you still think that we could do better, feel free to reopen this issue.
Installing this version
https://github.com/ossc-db/pg_hint_plan/releases/download/REL14_1_4_0/pg_hint_plan14-1.4-1.el8.x86_64.rpm
Testing to see how queries behave if there are errors in the hint. If there is no matching index in the
IndexScan
hint the planner estimates the cost to a really large number pushing the planner into JIT functions. See below where I have misspelled an index name. Not always likely but if a developer gets this wrong it could be quite damaging. Would there not be a way to ignore the hint if there is no matching index ?Also the logger shows the index as being used even though it does not exist.