Re: The use of cpu_index_tuple_cost by the query planner - Mailing list pgsql-novice

From Simon Riggs
Subject Re: The use of cpu_index_tuple_cost by the query planner
Date
Msg-id CA+U5nMLBeb8JUUyo7pxd5rmD27JvcFfQTO8uGb8ecW1U-P=vLQ@mail.gmail.com
Whole thread Raw
In response to The use of cpu_index_tuple_cost by the query planner  (Antonio Carlos Salzvedel Furtado Junior <acsfj08@inf.ufpr.br>)
Responses Re: The use of cpu_index_tuple_cost by the query planner
List pgsql-novice
On 27 June 2012 21:28, Antonio Carlos Salzvedel Furtado Junior
<acsfj08@inf.ufpr.br> wrote:

> I'm trying to understand the use of PostgreSQL tuning parameters by the
> query planner's cost estimator. I'm trying to use simple queries to
> understand how these parameters would affect the estimated cost. However, I
> haven't still been able to see the cpu_index_tuple_cost.

Your best hope is to read the source code. Things will become much clearer.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-novice by date:

Previous
From: Antonio Carlos Salzvedel Furtado Junior
Date:
Subject: The use of cpu_index_tuple_cost by the query planner
Next
From: Jeff Davis
Date:
Subject: Re: The use of cpu_index_tuple_cost by the query planner