Re: Timestamp indexes

select * from applicants as a where (a.created::date > '05-01-2000' or
a.resubmitted::date > '05-01-2000') order by (case when a.resubmitted >
a.created then a.resubmitted else a.created end) desc limit 10 offset 0

There is one of the queries.. I just remembered that the order by was added
since last time I checked it's PLAN (in the 6.5.X days) -- could that be the
problem?

8784 records in the applicant database.

created and resubmitted are both timestamps.

NOTICE: QUERY PLAN:

Sort (cost=2011.65..2011.65 rows=4880 width=611)
-> Seq Scan on applicants a (cost=0.00..1712.68 rows=4880 width=611)

ProcessQuery
! system usage stats:
! 7.489270 elapsed 5.609119 user 1.730936 system sec
! [5.618921 user 1.750540 sys total]
! 1/546 [1/546] filesystem blocks in/out
! 0/9287 [0/9496] page faults/reclaims, 0 [0] swaps
! 0 [0] signals rcvd, 0/3 [3/6] messages rcvd/sent
! 7/102 [10/105] voluntary/involuntary context switches
! postgres usage stats:
! Shared blocks: 0 read, 0 written, buffer hit rate
= 100.00%
! Local blocks: 0 read, 0 written, buffer hit rate
= 0.00%
! Direct blocks: 0 read, 0 written
CommitTransactionCommand

Thanks Tom!

-Mitch