From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Anj Adu <fotographs(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: slow index lookup |
Date: | 2010-06-23 01:10:15 |
Message-ID: | 1277255415.14943.20.camel@jd-desktop.unknown.charter.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 2010-06-22 at 18:00 -0700, Anj Adu wrote:
> i have several partitions like this (similar size ...similar data
> distribution)..these partitions are only "inserted"..never updated.
> Why would I need to vacuum..
>
An explain analyze is what is in order for further diagnosis.
JD
> I can reindex..just curious what can cause the index to go out of whack.
>
> On Tue, Jun 22, 2010 at 4:44 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > Excerpts from Anj Adu's message of mar jun 22 17:44:39 -0400 2010:
> >> This query seems unreasonable slow on a well-indexed table (13 million
> >> rows). Separate indexes are present on guardid_id , from_num and
> >> targetprt columns.
> >
> > Maybe you need to vacuum or reindex?
> >
> > --
> > Álvaro Herrera <alvherre(at)commandprompt(dot)com>
> > The PostgreSQL Company - Command Prompt, Inc.
> > PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> >
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
From | Date | Subject | |
---|---|---|---|
Next Message | Anj Adu | 2010-06-23 01:21:46 | Re: slow index lookup |
Previous Message | Anj Adu | 2010-06-23 01:00:29 | Re: slow index lookup |