User Tools

Site Tools


how_to:database_maintenance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
how_to:database_maintenance [2012/02/15 10:53] paulhow_to:database_maintenance [2012/04/16 13:48] – [Freeing disk space] paul
Line 24: Line 24:
 If you are very short of free disk space, then you can use the 'vacuumdb' program, but this is not recommended except as a last resort. To do this, run **vacuumdb -f -U vpop3 -p <portnumber> vpop3**. After you have run this you will need to reindex the database as well - use **reindexdb -U vpop3 -p <portnumber> vpop3**. This "vacuum full" operation will generally take a lot longer than the 'clusterdb' program. If you are very short of free disk space, then you can use the 'vacuumdb' program, but this is not recommended except as a last resort. To do this, run **vacuumdb -f -U vpop3 -p <portnumber> vpop3**. After you have run this you will need to reindex the database as well - use **reindexdb -U vpop3 -p <portnumber> vpop3**. This "vacuum full" operation will generally take a lot longer than the 'clusterdb' program.
  
 +Another way of freeing disk space is to do a [[backup_vpop3#manual_database_backup|database backup]] & [[restore_a_backup_of_vpop3|restore]]. Again, this requires VPOP3 to be stopped while it is performed.
 =====Rebuilding Indexes===== =====Rebuilding Indexes=====
 If you suspect that indexes have become damaged, then you can reindex the database. Again, this requires VPOP3 to be stopped first. If you suspect that indexes have become damaged, then you can reindex the database. Again, this requires VPOP3 to be stopped first.
how_to/database_maintenance.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1