database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-02 09:02:37 +03:00
Code Activity

Make cost estimates for SubqueryScan more realistic: charge cpu_tuple_cost

Browse Source 
for each row processed, and don't forget the evaluation cost of any
restriction clauses attached to the node.  Per discussion with Greg Stark.
This commit is contained in:
Tom Lane
2003-07-14 22:35:54 +00:00
parent b800196230
commit 3d09f6c560
4 changed files with 53 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/optimizer/util/pathnode.c
View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/optimizer/util/pathnode.c,v 1.91 2003/06/29 23:05:04 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/optimizer/util/pathnode.c,v 1.92 2003/07/14 22:35:54 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -686,9 +686,7 @@ create_subqueryscan_path(RelOptInfo *rel, List *pathkeys)
pathnode->parent = rel;
pathnode->pathkeys = pathkeys;
/* just copy the subplan's cost estimates */
pathnode->startup_cost = rel->subplan->startup_cost;
pathnode->total_cost = rel->subplan->total_cost;
cost_subqueryscan(pathnode, rel);
return pathnode;
}