Column-Store Tables Cannot Be Updated or Table Bloat Occurs

Symptom

• The column-store table fails to be updated.
• When a column-store table is updated for multiple times, the table size is expanded by more than 10 times.

Possible Causes

• Column-store tables cannot be updated concurrently.
• When a column-store table is updated, the space does not reclaim old records.

Handling Procedure

• Method 1

This method is supported only by 8.1.3 and later cluster versions.

1. Log in to the GaussDB(DWS) management console.
2. Click the name of the target cluster.
3. In the navigation pane, choose Intelligent O&M.
4. Click the O&M Plan tab. Click Add O&M Task.

   

5. The Add O&M Task page is displayed.
   • Select a Vacuum task.
   • Select Specify for Scheduling Mode. The intelligent O&M module automatically delivers table-level Vacuum tasks in the specified time window.

     You can enter column-store tables that require Vacuum. Each row corresponds to a table, which contains database name, schema name, and table name, separated by spaces.

     

6. Click Next: Configure Schedule to configure the schedule and Vacuum type. You are advised to select Periodic for Task Type. The GaussDB(DWS) automatically executes VACUUM in your selected time windows.

   

7. After confirming that the information is correct, click Next to complete the configuration.

• Method 2

After updating column-store tables, you perform VACUUM FULL to clear the tables. For details, see VACUUM"VACUUM" in .

1

VACUUM FULL table_name;