using hints
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- Avg merge
- 3h 7m
- Merged PRs (30d)
- 13
Description
https://github.com/ossc-db/pg_hint_plan?tab=readme-ov-file
eg to force use of an index
DBI::dbExecute(db, "SET enable_hashjoin TO OFF;")
DBI::dbExecute(db, "SET enable_seqscan TO OFF;")
-> Query (join etc that is going to an inefficient sequential scan)
DBI::dbExecute(db, "RESET enable_hashjoin;")
DBI::dbExecute(db, "RESET enable_seqscan;")
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked pg_hint_plan README and the shown DBI::dbExecute statements first. The issue does not identify an entry point, tests, or a defined completion condition, so confirm the intended scope and acceptance criteria before estimating a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, r
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100