Help Center/ GaussDB/ Developer Guide(Centralized_V2.0-8.x)/ Best Practices/ Best Practices for VACUUM/ FAQ/ Possible Causes of Data Table Bloat/ FSM Is Damaged

Updated on 2025-05-29 GMT+08:00

View PDF

FSM Is Damaged

Symptom

FSM is a mechanism used to maintain free space of data pages. Each FSM entry uses 8 bits to describe the free space of a page. The allocation of all data pages and space management depend on the accuracy of this mechanism. If FSM is inaccurate, free pages may fail to be obtained, triggering the page extension logic.

Fault Locating

In GaussDB 505.2, the spatial accuracy analysis view is introduced. Such problems can be quickly analyzed and located.

Workarounds

Perform VACUUM manually to rebuild FSM of the target table and quickly restore the FSM accuracy.

Parent topic: Possible Causes of Data Table Bloat

Previous topic: AUTOVACUUM Cleanup Efficiency Is Low

Next topic: How Do I Estimate the Current Table or Database Space Bloat Ratio?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.