From: | hubert depesz lubaczewski <depesz(at)depesz(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 12:55:36 |
Message-ID: | 20111004125536.GA21733@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Oct 03, 2011 at 02:48:10PM -0300, Soporte @ TEKSOL S.A. 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?
general answer:
http://www.depesz.com/index.php/2010/09/09/why-is-my-index-not-being-used/
but for more details, we'd need to see the query and \d of the table.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2011-10-04 13:01:34 | Re: pkey is not used on productive database |
Previous Message | Venkat Balaji | 2011-10-04 11:23:10 | Re: : PG9.0 - Checkpoint tuning and pg_stat_bgwriter |