From: | "David Monarchi" <david(dot)e(dot)monarchi(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | unreasonable run time for vacuum analyze? |
Date: | 2007-06-13 00:04:01 |
Message-ID: | eea51fdb0706121704p2366a299uf1068bc2c28e9689@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hello -
I'm running 8.2.3 on an 8-processor Linux box with a fiber-optic SAN.
One table in the database contains 22.6M rows of 71 fields with an average
length of about 500 bytes. The table is in BCNF. The table is queried in a
wide variety of ways. There are 37 btree and Gin indexes defined on the
table. The GIN indexes are on array fields. The rest are btree.
I started running vacuum analyze on this table over 44 hours ago, and it is
still running. The load on the machine has been modest. There have been no
times when all eight processors were being used.
1) is this amount of time reasonable?
2) if I abort the vacuum analyze, will I corrupt the table, its indexes, or
the database?
3) are there parameters that I can set to improve the performance of the
vacuum analyze process?
Thank you,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2007-06-13 00:25:14 | Re: unreasonable run time for vacuum analyze? |
Previous Message | Richard Broersma Jr | 2007-06-12 23:37:08 | Re: no results for nextval() query? |