pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Soporte @ TEKSOL S.A. <soporte@teksol.com.ar>
To: pgsql-performance@postgresql.org
Subject: pkey is not used on productive database
Date: Mon, 3 Oct 2011 14:48:10 -0300
Message-ID: <014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar> (raw)

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

 

view thread (3+ messages)  latest in thread

Message-ID: <014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar>
Permalink:  ../014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar/
Also on:    postgresql.org/message-id/014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: soporte@teksol.com.ar
  Subject: Re: pkey is not used on productive database
  In-Reply-To: <014c01cc81f4$a774e140$f65ea3c0$@teksol.com.ar>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox