Re: index / sequential scan problem - Mailing list pgsql-performance

From Paul Thomas
Subject Re: index / sequential scan problem
Date
Msg-id 20030717111248.C27264@bacon
Whole thread Raw
In response to index / sequential scan problem  (Fabian Kreitner <fabian.kreitner@ainea-ag.de>)
Responses Re: index / sequential scan problem  (Fabian Kreitner <fabian.kreitner@ainea-ag.de>)
List pgsql-performance
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.

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

--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants         |
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+

pgsql-performance by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Re: index / sequential scan problem
Next
From: Vincent van Leeuwen
Date:
Subject: Re: Hardware performance