Tom Lane wrote:

Jean-Paul ARGUDO <jean-paul.argudo@idealx.com> writes:

EXPLAIN SELECT t12_bskid, t12_pnb, t12_lne, t12_tck
FROM T12_20011231
WHERE t12_bskid >= 1   
ORDER BY t12_bskid, t12_pnb, t12_tck, t12_lne;

Sort  (cost=3006.13..3006.13 rows=25693 width=46)
  ->  Seq Scan on t12_20011231  (cost=0.00..1124.20 rows=25693 width=46)

Try the following:

EXPLAIN ANALYZE SELECT t12_bskid, t12_pnb, t12_lne, t12_tck FROM T12_20011231 WHERE t12_bskid >= 1 ORDER BY t12_bskid, t12_pnb, t12_tck, t12_lne;

and see what the actual results are. Then turn the seq_scans off and do the same thing.

=> Uh? Seq scan cheaper than index???


For that kind of query, very probably.  How much of the table is
actually selected by "WHERE t12_bskid >= 1"?

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)