From d4ce5a4f4c3516e88fa34c53bcc7313db90a3c08 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 12 Jan 2003 22:35:29 +0000 Subject: Revise cost_qual_eval() to compute both startup (one-time) and per-tuple costs for expression evaluation, not only per-tuple cost as before. This extension is needed in order to deal realistically with hashed or materialized sub-selects. --- doc/src/sgml/indexcost.sgml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/indexcost.sgml b/doc/src/sgml/indexcost.sgml index 63cf8daf22d..2e62280a8be 100644 --- a/doc/src/sgml/indexcost.sgml +++ b/doc/src/sgml/indexcost.sgml @@ -1,5 +1,5 @@ @@ -237,9 +237,10 @@ amcostestimate (Query *root, * Also, we charge for evaluation of the indexquals at each index tuple. * All the costs are assumed to be paid incrementally during the scan. */ - *indexStartupCost = 0; + cost_qual_eval(&index_qual_cost, indexQuals); + *indexStartupCost = index_qual_cost.startup; *indexTotalCost = numIndexPages + - (cpu_index_tuple_cost + cost_qual_eval(indexQuals)) * numIndexTuples; + (cpu_index_tuple_cost + index_qual_cost.per_tuple) * numIndexTuples; -- cgit v1.2.3