Changes between Version 4 and Version 5 of DbPurge

Timestamp:

Sep 18, 2009, 4:08:48 PM (15 years ago)

Author:

davea

Comment:

--

DbPurge

@@ -1 +1 @@
 = Database purging utility =
 
-As a BOINC project operates, the size of its workunit and result tables increases. Eventually they become so large that adding a field or building an index may take hours or days.
-To address this problem, BOINC provides a utility '''db_purge''' that writes result and WU records to XML-format archive files, then deletes them from the database.
-Workunits are purged only when their input files have been deleted. Because of BOINC's file-deletion policy, this implies that all results are completed. So when a workunit is purged, all its results are purged too.
+As a BOINC project operates, the size of its workunit and result tables increases.
+Eventually they become so large that adding a field or building an index may take hours or days.
+To keep this from happening, BOINC provides a utility '''db_purge'''
+that writes result and WU records to XML-format archive files,
+then deletes them from the database.
+Workunits are purged only when their input files have been deleted.
+Because of BOINC's file-deletion policy, this implies that all results are completed.
+So when a workunit is purged, all its results are purged too.
 
 db_purge creates an archive/ directory and stores archive files there.
 
-db_purge is normally run as a daemon, specified in the [ProjectConfigFile config.xml] file. It has the following command-line options: 
+db_purge is normally run as a daemon, specified in the [ProjectConfigFile config.xml] file.
+It has the following command-line options: 
 
  '''-min_age_days N '''::