pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: AI Rumman <rummandba@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why primary key index are not using in joining?
Date: Mon, 15 Feb 2010 02:50:13 -0700
Message-ID: <dcc563d11002150150u2108f59eh7c5f2015cf47d367@mail.gmail.com> (raw)
In-Reply-To: <2a7905441002150135x1ba61b19p89f3c3b94d252843@mail.gmail.com>
References: <2a7905441002150135x1ba61b19p89f3c3b94d252843@mail.gmail.com>

On Mon, Feb 15, 2010 at 2:35 AM, AI Rumman <rummandba@gmail.com> wrote:
>
> Please have a look at the following explain plan:
>
> explain analyze
> select *
> from vtiger_crmentity
> inner JOIN vtiger_users
>          ON vtiger_users.id = vtiger_crmentity.smownerid
> where vtiger_crmentity.deleted = 0  ;
>
> QUERY
> PLAN
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>  Hash Join  (cost=3665.17..40019.25 rows=640439 width=1603) (actual
> time=115.613..3288.436 rows=638081 loops=1)
>    Hash Cond: ("outer".smownerid = "inner".id)
>    ->  Bitmap Heap Scan on vtiger_crmentity  (cost=3646.54..30394.02
> rows=640439 width=258) (actual time=114.763..986.504 rows=638318 loops=1)
>          Recheck Cond: (deleted = 0)
>          ->  Bitmap Index Scan on vtiger_crmentity_deleted_idx
> (cost=0.00..3646.54 rows=640439 width=0) (actual time=107.851..107.851
> rows=638318 loops=1)
>                Index Cond: (deleted = 0)
>    ->  Hash  (cost=18.11..18.11 rows=211 width=1345) (actual
> time=0.823..0.823 rows=211 loops=1)
>          ->  Seq Scan on vtiger_users  (cost=0.00..18.11 rows=211
> width=1345) (actual time=0.005..0.496 rows=211 loops=1)
>  Total runtime: 3869.022 ms
>
> Sequential index is occuring on vtiger_users table while it has primary key
> index on id.
> Could anyone please tell me why?

Cause it's only 211 rows and only takes 0.5 milliseconds to scan?



view thread (4+ messages)  latest in thread

Message-ID: <dcc563d11002150150u2108f59eh7c5f2015cf47d367@mail.gmail.com>
Permalink:  ../dcc563d11002150150u2108f59eh7c5f2015cf47d367@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d11002150150u2108f59eh7c5f2015cf47d367@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: scott.marlowe@gmail.com, rummandba@gmail.com
  Subject: Re: Why primary key index are not using in joining?
  In-Reply-To: <dcc563d11002150150u2108f59eh7c5f2015cf47d367@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