| From: | "Soporte (at) TEKSOL S(dot)A(dot)" <soporte(at)teksol(dot)com(dot)ar> |
|---|---|
| To: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | pkey is not used on productive database |
| Date: | 2011-10-03 17:48:10 |
| Message-ID: | 014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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?
Cristian C. Bittel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcin Mańk | 2011-10-03 22:45:47 | Re: Query with order by and limit is very slow - wrong index used |
| Previous Message | Venkat Balaji | 2011-10-03 16:54:19 | Re: : Performance Improvement Strategy |