pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Sacks <josh.sacks@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Not using Primary Key in query
Date: Tue, 25 May 2004 11:37:55 -0700
Message-ID: <b31c861a04052511379c8f62e@mail.gmail.com> (raw)

I can't understand what's going on in this simple query:

select c.name from Candidate C where
  C.candidate_id in (select candidate_id from REFERRAL R
                     where  r.employee_id = 3000);


Where Candidate.CANDIDATE_ID is the primary key for Candidate.
Here's the EXPLAN ANALYZE:

Seq Scan on candidate c  (cost=100000000.00..100705078.06 rows=143282 width=18) 
                                    (actual time=2320.01..2320.01
rows=0 loops=1)
   Filter: (subplan)
   SubPlan
     ->  Materialize  (cost=2.42..2.42 rows=3 width=4) 
                           (actual time=0.00..0.00 rows=0 loops=286563)
           ->  Index Scan using referral_employee_id_index on referral r  
                   (cost=0.00..2.42 rows=3 width=4) (actual
time=0.48..0.48 rows=0 loops=1)
                 Index Cond: (employee_id = 3000)


It seems to be accurately estimating the number of rows returned by
the sub-query (3), but then it thinks that 143282 rows are going to be
returned by the main query, even though we are querying based on the
PRIMARY KEY!


To prove that in index query is possible, I tried:
select c.name from Candidate C where
  C.candidate_id in (99, 22, 23123, 2344)  which resulted in:

Index Scan using candidate_id_index, candidate_id_index,
candidate_id_index, candidate_id_index on candidate c
     (cost=0.00..17.52 rows=4 width=18) (actual time=24.437..29.088
rows=3 loops=1)
   Index Cond:
    ((candidate_id = 99) OR (candidate_id = 22) OR 
      (candidate_id = 23123) OR (candidate_id = 2344))


Any ideas what's causing the query planner to make such a simple and
drastic error?

Thanks,
Josh



view thread (2+ messages)  latest in thread

Message-ID: <b31c861a04052511379c8f62e@mail.gmail.com>
Permalink:  ../b31c861a04052511379c8f62e@mail.gmail.com/
Also on:    postgresql.org/message-id/b31c861a04052511379c8f62e@mail.gmail.com

 · 

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: josh.sacks@gmail.com
  Subject: Re: Not using Primary Key in query
  In-Reply-To: <b31c861a04052511379c8f62e@mail.gmail.com>

* 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