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)

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)