pgadmin-org / pgadmin-org/pgadmin4
Add support for VACUUM ONLY syntax
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
PG 18 and above
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
The issue only identifies VACUUM ONLY syntax for PostgreSQL 18 and above. First locate pgAdmin's existing VACUUM support and its related tests, then determine where the new syntax must be accepted or exposed. Done means PostgreSQL 18 users can use VACUUM ONLY correctly without breaking existing VACUUM behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100