From: | John A Meinel <john(at)arbash-meinel(dot)com> |
---|---|
To: | "Tomeh, Husam" <htomeh(at)firstam(dot)com> |
Cc: | Luke Lonergan <llonergan(at)greenplum(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: "Vacuum Full Analyze" taking so long |
Date: | 2005-07-25 23:31:08 |
Message-ID: | 42E5763C.7030804@arbash-meinel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tomeh, Husam wrote:
>
> Nothing was running except the job. The server did not look stressed out
> looking at top and vmstat. We have seen slower query performance when
> performing load tests, so I run the re-index on all application indexes
> and then issue a full vacuum. I ran the same thing on a staging server
> and it took less than 12 hours. Is there a possibility the DB pages are
> corrupted. Is there a command to verify that. (In Oracle, there's a
> dbverify command that checks for corruption on the data files level).
>
> The other question I have. What would be the proper approach to rebuild
> indexes. I re-indexes and then run vacuum/analyze. Should I not use the
> re-index approach, and instead, drop the indexes, vacuum the tables, and
> then create the indexes, then run analyze on tables and indexes??
I *think* if you are planning on dropping the indexes anyway, just drop
them, VACUUM ANALYZE, and then recreate them, I don't think you have to
re-analyze after you have recreated them.
John
=:->
>
> Thanks,
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2005-07-26 00:31:02 | Re: COPY insert performance |
Previous Message | Tomeh, Husam | 2005-07-25 23:14:16 | Re: "Vacuum Full Analyze" taking so long |