Skip to content

Commit b04045b

Browse files
Update articles/postgresql/flexible-server/how-to-pgdump-restore.md
Co-authored-by: Sarah Gaspari <[email protected]>
1 parent f398dae commit b04045b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/postgresql/flexible-server/how-to-pgdump-restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Before the starting the pg_dump process, consider if table vacuuming is necessar
4242
select schemaname,relname,n_dead_tup,n_live_tup,round(n_dead_tup::float/n_live_tup::float*100) dead_pct,autovacuum_count,last_vacuum,last_autovacuum,last_autoanalyze,last_analyze from pg_stat_all_tables where n_live_tup >0;
4343
```
4444

45-
The **dead_pct** column in the above query gives percentage of dead tuples when compared to live tuples.A high dead_pct value for a table might point to the table not being properly vacuumed.For tuning autovacuum, review the article [Autovacuum Tuning](./how-to-autovacuum-tuning.md).
45+
The **dead_pct** column in the above query gives percentage of dead tuples when compared to live tuples. A high dead_pct value for a table might point to the table not being properly vacuumed. For tuning autovacuum, review the article [Autovacuum Tuning](./how-to-autovacuum-tuning.md).
4646

4747

4848
As a one of case perform manual vacuum analyze of the tables that are identified.

0 commit comments

Comments
 (0)