Project

General

Profile

« Previous | Next » 

Revision 13028

Added by Aaron Marcuse-Kubitza about 10 years ago

/README.TXT: Full database import: disk space: documented that the entire disk again gets used long after the beginning of the import, when only a few datasources are running (ie. it definitely seems to be a recent bug in Postgres, and not a latent problem)

View differences:

README.TXT
82 82 
			again. (the high-water mark varies by import.)
83 83 
		although the import schema itself is only 315 GB, Postgres uses
84 84 
			significant temporary space at the beginning of the import.
85 
			the total disk usage oscillates between 1.2-1.8 TB in the first
86 
			3+ hours (for import started @12:55:09, high-water marks of
87 
			1.7 TB @14:00:25, 1.8 TB @15:38:32).
85 
			the total disk usage oscillates between 1.2 TB and the entire disk
86 
			for the first day (for import started @12:55:09, high-water marks of
87 
			1.7 TB @14:00:25, 1.8 TB @15:38:32, entire disk for 4 min
88 
			@05:35:44 w/ only a few datasources running).
88 89 
		To free up space, remove backups that have been archived on jupiter:
89 90 
			List backups/ to view older backups
90 91 
			Check their MD5 sums using the steps under On jupiter below

Also available in: Unified diff