Re: reducing random_page_cost from 4 to 2 to force index scan - Mailing list pgsql-performance

From Nathan Boley
Subject Re: reducing random_page_cost from 4 to 2 to force index scan
Date
Msg-id BANLkTimOEkO55L4g8u7-zyXwTnxFDjhpbA@mail.gmail.com
Whole thread Raw
In response to Re: reducing random_page_cost from 4 to 2 to force index scan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: reducing random_page_cost from 4 to 2 to force index scan
List pgsql-performance
> The accesses to an index are far more likely to be clustered than the
> accesses to the underlying table, because the index is organized in a
> way that's application-meaningful and the table not so much.

So, to clarify, are you saying that if query were actually requesting
rows uniformly random, then there would be no reason to suspect that
index accesses would have hotspots? It seems like the index structure
( ie, the top node in b-trees ) could also get in the way.

Best,
Nathan

pgsql-performance by date:

Previous
From: Jeff
Date:
Subject: Re: Using pgiosim realistically
Next
From: Tom Lane
Date:
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan