Re: index on INT8 column is never used - Mailing list pgsql-general

From Shridhar Daithankar
Subject Re: index on INT8 column is never used
Date
Msg-id 200305052113.20155.shridhar_daithankar@nospam.persistent.co.in
Whole thread Raw
In response to index on INT8 column is never used  (Maurice Balick <balm@smiley.com>)
List pgsql-general
On Monday 05 May 2003 20:24, Maurice Balick wrote:
> nf=# explain select account_id from transactions where timestamp =
> 1052101817212;
> NOTICE:  QUERY PLAN:
>
> Seq Scan on transactions  (cost=0.00..40414.88 rows=3855 width=4)

Try
 nf=# explain select account_id from transactions where timestamp =
 1052101817212::int8;

That is postgresql's way of typecasting. It is probably first in the FAQ...

But BTW, if it is returning 4000 rows, it might still default to sequential
scan.. You need to lower random_page_cost in postgresql.conf to raise the
threshold at which pg flips from index scan to seq. scan..

HTH

 Shridhar

--
Nasrudin was carrying home a piece of liver and the recipe for liver
pie.  Suddenly a bird of prey swooped down and snatched the piece of
meat from his hand.  As the bird flew off, Nasrudin called after it,
"Foolish bird!  You have the liver, but what can you do with it without
the recipe?"


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: Database server restarting
Next
From: "Bob Krus"
Date:
Subject: GENERAL: PosgreSQL Inquiry