cloudberry-contrib / cloudberry-contrib/pgvector
[Bug] Fix GUC ivfflat.max_probes
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
pgvector and Cloudberry Database version
The GUC ivfflat.max_probes is used to control the number of results like limit, but in cbdb, data is distributed in different segments, the GUC should be adapted in MPP env.
What happened
GUC ivfflat.max_probes in cbdb env.
What you think should happen instead
No response
How to reproduce
make installcheck
Operating System
CentOS
Anything else
No response
Are you willing to submit PR?
- Yes, I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct.
Contributor guide
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
Start by locating the definition and uses of the ivfflat.max_probes GUC and review how it behaves across Cloudberry Database segments. Run make installcheck to reproduce the current behavior; done means the setting correctly accounts for distributed execution in an MPP environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100