[Bug] Abnormal Bloat of the mgt_rule_detect_log_detail table
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
What happened?
The mgt_rule_detect_log_detail table occupies 358 GB of disk space, while the actual amount of useful data and indexes is significantly less. Standard cleaning procedures (DELETION + VACUUMING) do not return free space to the operating system, which creates the risk of an emergency filling of the disk (database failure).
Table: public.mgt_rule_detect_log_detail
Current disk size: 358 GB
The size of the indexes: 1.6 GB (extremely small for such a volume of data)
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
Start by investigating the public.mgt_rule_detect_log_detail table and the reported difference between its 358 GB disk usage and its 1.6 GB of indexes. Reproduce the cleanup behavior involving deletion and VACUUM, then determine what change would reliably return unused space to the operating system. Done means the table no longer risks exhausting disk space after cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100