From: | raghavendra t <raagavendra(dot)rao(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to fast the REINDEX |
Date: | 2010-03-31 22:00:52 |
Message-ID: | m2nbc7de5a31003311500sce514e92k796870a663b38438@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Thank you for the suggestion.
On Thu, Apr 1, 2010 at 3:21 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov>wrote:
> raghavendra t <raagavendra(dot)rao(at)gmail(dot)com> wrote:
>
> > my question is, how to get a performance on the existing indexes.
> > You mean to say , drop the existing indexes and create the index
> > with CONCURRENTLY. Does this give the performance back.
>
> You would normally want to create first and then drop the old ones,
> unless the old ones are hopelessly corrupted. Since you still
> haven't given me any information to suggest you need to reindex
> except for the mention of corruption, or any information to help
> identify where the performance bottleneck is, I can't see any other
> improvements to suggest at this point.
>
> -Kevin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-03-31 22:10:52 | Re: How to fast the REINDEX |
Previous Message | Kevin Grittner | 2010-03-31 21:51:55 | Re: How to fast the REINDEX |