Re: Dissapearing indexes, what's that all about?

Daniel ?erud  writes:
> Can't see the logic behind that though
> The jump in the b-tree must save about 5000 checks... half 
> the table??

CPUs are fast.  Disks are slow.  If you think about CPU time rather
than disk accesses, you will usually draw the wrong conclusions.

Even more to the point, disks do not like random access.  A seqscan
can typically fetch four or more sequential blocks from disk in the
time it takes an indexscan to fetch one block on a random-access basis.

When you do the math it turns out seqscan wins unless you are fetching
just a small percentage of the rows.

			regards, tom lane