Received: from bjke.com (firewall-user@ganymede.bjke.com [144.210.8.38]) by hub.org (8.9.2/8.9.1) with ESMTP id NAA13339 for ; Tue, 2 Feb 1999 13:26:51 -0500 (EST) (envelope-from djackson@cpsgroup.com) Received: by bjke.com; id MAA11783; Tue, 2 Feb 1999 12:26:48 -0600 (CST) Received: from cpsmail.cpsgroup.com(144.210.12.11) by gauntlet.bjke.com via smap (4.1) id xmaa11186; Tue, 2 Feb 99 12:26:18 -0600 Received: by cpsmail with Internet Mail Service (5.0.1458.49) id ; Tue, 2 Feb 1999 12:28:44 -0600 Message-ID: From: "Jackson, DeJuan" To: Vladimir Dobrokhotov , pgsql-sql@postgreSQL.org Subject: RE: [SQL] index on int2. Date: Tue, 2 Feb 1999 12:28:41 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain > Hello, > > I create index on int2 field, and it never used: > > create index xxx on ttt using btree(int2_field); > vacuum ttt; (2600 tuples) > explain select * from ttt where int2_field>1; > ... Seq Scan on ttt ... > > What I need to do to use index search? > > Thanks. > Vladimir Dobrokhotov I don't think you got an answer for this yet so... Think of it this way... Is it cheaper to go the disk read in an index and relate those to the rows of the table concerned, then go and fetch each of the pages required to print out the results requested? The answer to that question depends on the percentage of table pages that will need to be loaded anyway. So, (wisely IMHO) Postgres say "Hey you're about to load in over 3/4 of this table why should I waste the seek time to load in the index as well when I mostly won't be using it. So I guess I'll just load em' all in, which with a good file system and caching is faster than seeking for the pages in index order, and just run your little int compare over those rows for ya." If you want to see if your index is being used try '=' instead of '>'. Hope this helps, -DEJ