From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Soporte (at) TEKSOL S(dot)A(dot)" <soporte(at)teksol(dot)com(dot)ar> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pkey is not used on productive database |
Date: | 2011-10-04 13:01:34 |
Message-ID: | CAOR=d=2iS-kuQc+Bk0sz=3x0PMBYTj1ScPs6QLpEQ7+AD07NDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Oct 3, 2011 at 11:48 AM, Soporte @ TEKSOL S.A.
<soporte(at)teksol(dot)com(dot)ar> wrote:
> Hi,
>
> I need help to understand the issue on a productive database for a select
> that takes more time than expected.
> 1- On a development database I ran the query (select) and I can see on
> Explain Analyze pgAdmin use all the indexes and primary keys defined. Dev db
> has almost 10% of productive data.
>
> 2- On productive database the same query on Explain Analyze from
> pgAdmin shows a diferent planning, not using a pkey index and instead uses
> the progressive scan on a million of rows. I can see Primary key is defined
> for the table on pgAdmin.
>
> What could be the issue on a productive for not use the pkey index for the
> SELECT?
Please post the schema, query and explain analyze output of the runs
on both machines.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Klemme | 2011-10-04 13:27:49 | Re: Window functions and index usage |
Previous Message | hubert depesz lubaczewski | 2011-10-04 12:55:36 | Re: pkey is not used on productive database |