From: John A Meinel <john@arbash-meinel.com>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: "Vacuum Full Analyze" taking so long
Date: Mon, 25 Jul 2005 18:31:08 -0500
Message-ID: <42E5763C.7030804@arbash-meinel.com> (raw)
In-Reply-To: <C45835824D00A844BBD0F032D5CDED920116DC12@pisgana01sxch01.ana.firstamdata.com>
References: <C45835824D00A844BBD0F032D5CDED920116DC12@pisgana01sxch01.ana.firstamdata.com>
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,
>
>
Attachments:
signature.asc (application/pgp-signature, 252B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: john@arbash-meinel.com, htomeh@firstam.com, llonergan@greenplum.com
Subject: Re: "Vacuum Full Analyze" taking so long
In-Reply-To: <42E5763C.7030804@arbash-meinel.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox