On Jan 9, 2008 11:39 AM, Andrew Sullivan <ajs@xxxxxxxxxxxxxxx> wrote:
On Wed, Jan 09, 2008 at 05:28:15PM +0100, Ivan Sergio Borgonovo wrote:Well, this is more or less what CLUSTER does. There are some cases where
> Does it make any sense *knowing* how the implementation works to load
> records in a table in a specific order to improve performances?
happening to know about the order the table is in will yield happy effects,
yes.
You are right. Sometimes when i cluster the table according to the frequently accessed indexes then it makes queries pretty fast. But its not a feasible solution always since some tables have more indexes which are accessed frequently. So clustering the table according to one index will yield poor performance to queries involving other indexes. Index-only scan is a good solution for this I guess for queries involving indexed columns (like in oracle) !!!
josh
