Re: A costing analysis tool - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: A costing analysis tool
Date
Msg-id 200510161423.41423.josh@agliodbs.com
Whole thread Raw
In response to Re: A costing analysis tool  (Greg Stark <gsstark@mit.edu>)
Responses Re: A costing analysis tool
Re: A costing analysis tool
List pgsql-hackers
Greg,

> Or something like that. It might require breaking random_page_cost into two
> or three different parameters that would normally have the same cost but
> aren't handled the same, like random_heap_cost, random_leaf_cost, and
> random_nonleaf_cost.

Gods forbid.   People don't know how to use random_page_cost as it is; how are 
they going to handle having 5 different parameters?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: slow IN() clause for many cases
Next
From: Josh Berkus
Date:
Subject: Re: A costing analysis tool