pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Robert Treat <xzilla@users.sourceforge.net>
To: Anshaj <anshaj@in2m.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: indexes are not working for
Date: Fri, 22 Oct 2004 08:54:28 -0400
Message-ID: <200410220854.28954.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0410221037000.5072-100000@Unforgiven>
References: <Pine.LNX.4.44.0410221037000.5072-100000@Unforgiven>

Please do not post new topic as reply's to unrelated threads!!

On Friday 22 October 2004 02:10, Anshaj wrote:
> Dear group,
>
>          I have a table foo
> anshajdb=# \d foo
>            Table "public.foo"
>  Column  |       Type        | Modifiers
> ---------+-------------------+-----------
>  snumber | numeric(18,0)     |
>  test    | character varying |
> Indexes:
>     "snum_idx" btree (snumber)
>
> when I try to do a query like
> explain analyze select * from foo where snumber > 1000;
>
> Seq Scan on foo  (cost=0.00..69.00 rows=320 width=391) (actual
> time=0.011..0.721 rows=323 loops=1)
>    Filter: (snumber > 1000::numeric)
>  Total runtime: 0.979 ms
> (3 rows)
> It do a sequence scan on table. Why it is not using the snum_idx in this
> query. Do I need to change some setting or indexes don't work on this
> types of query.
>

You query is not selective enough for the database to use an index. ie. your 
retrieving 323 rows from at best 1323 rows in the table, so the database 
figures it can grab all of the records much faster by just doing a seq scan 
on the table.   Try adding some more data to the table and/or selecting a 
specific value and you'll see your index get used.     

-- 
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL



view thread (3+ messages)  latest in thread

Message-ID: <200410220854.28954.xzilla@users.sourceforge.net>
Permalink:  ../200410220854.28954.xzilla@users.sourceforge.net/
Also on:    postgresql.org/message-id/200410220854.28954.xzilla@users.sourceforge.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: xzilla@users.sourceforge.net, anshaj@in2m.com
  Subject: Re: indexes are not working for
  In-Reply-To: <200410220854.28954.xzilla@users.sourceforge.net>
  References: <Pine.LNX.4.44.0410221037000.5072-100000@Unforgiven> <200410220854.28954.xzilla@users.sourceforge.net>

* 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