From: | Aldor <an(at)mediaroot(dot)de> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | How to VACUUM this table? "998994633 estimated total rows" |
Date: | 2006-02-11 03:15:31 |
Message-ID: | 43ED56D3.7040404@mediaroot.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Hi,
I'm just curious about a VACUUM plan of this table:
1st) When to do VAUUM?
2nd) How often to do VACUUM?
3rd) With which postgresql.conf paremeters to set up vacuum?
4th) When to do a VACUUM FULL?
5th) Can autovacuum of 8.1 be used in this case?
I'm a little bit afraid about the size of the table, but I think
somebody should have a solution...
Here is the complete ANALYZE output of the table:
INFO: "tbl1": scanned 300 of 27744713 pages, containing 10802 live rows
and 0 dead rows; 300 rows in sample, 998994633 estimated total rows
The size of the data is 340 GB, this are 40% of the disk-array.
Thanks is advance.
Marco
From | Date | Subject | |
---|---|---|---|
Next Message | Nalin Bakshi | 2006-02-11 05:18:08 | Writing to a flat file using procedures |
Previous Message | uwcssa | 2006-02-11 01:47:34 | gepo optimizer question |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2006-02-11 04:48:53 | Getting the length of varlength data using PG_DETOAST_DATUM_SLICE or similar? |
Previous Message | Mark Kirkwood | 2006-02-11 01:57:28 | Re: What do the Windows pg hackers out there like for dev |