Re: Cluster vs. non-cluster query planning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nolan Cafferky <Nolan(dot)Cafferky(at)rbsinteractive(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Cluster vs. non-cluster query planning
Date: 2006-05-01 20:30:44
Message-ID: 8044.1146515444@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Nolan Cafferky <Nolan(dot)Cafferky(at)rbsinteractive(dot)com> writes:
> After some more digging on the mailing list, I found some comments on
> effective_cache_size. Bringing it up from the default of 1000 does pust
> the estimated cost for the index scan below that of the sequential scan,
> but not by much.

The first-order knob for tuning indexscan vs seqscan costing is
random_page_cost. What have you got that set to?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Nolan Cafferky 2006-05-01 21:08:01 Re: Cluster vs. non-cluster query planning
Previous Message Nolan Cafferky 2006-05-01 19:48:34 Re: Cluster vs. non-cluster query planning