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 [2013/09/09 10:16] – [Freeing disk space] paulhow_to:database_maintenance [2013/09/09 10:17] – [Alternative to backup/restore] paul
Line 41: Line 41:
 ====Alternative to backup/restore==== ====Alternative to backup/restore====
  
-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, stopVPOP3, then 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 a backup/restore 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, stop VPOP3, then run **[[http://www.postgresql.org/docs/9.1/static/app-vacuumdb.html|vacuumdb]] -f -U vpop3 -p <portnumber> vpop3**. After you have run this you will need to reindex the database as well - use **[[http://www.postgresql.org/docs/9.1/static/app-reindexdb.html|reindexdb]] -U vpop3 -p <portnumber> vpop3**. This "vacuum full" operation will generally take a lot longer than a backup/restore program.
 =====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