Re: index / sequential scan problem

At 12:12 17.07.2003, you wrote:

>On 17/07/2003 10:01 Fabian Kreitner wrote:
>
>Hi Fabian,
>
>When you are doing these kinds of tests, you need to be aware that the
>kernel may have most of your data cached after the first query and this
>may be why the second query appears to run faster.

I thought of this too, but executions times wont change with repeating /
alternating these two tests.

>Also don't be worried if the planner chooses a seq scan for small tables
>as the whole table can often be bought into memory with one IO whereas
>reading the index then the table would be 2 IOs. HTH

That is what I read too and is why Im confused that the index is indeed
executing faster. Can this be a problem with the hardware and/or postgress
installation?

Thanks,
Fabian