-
- Downloads
Make cost estimates for SubqueryScan more realistic: charge cpu_tuple_cost
for each row processed, and don't forget the evaluation cost of any restriction clauses attached to the node. Per discussion with Greg Stark.
Showing
- src/backend/optimizer/path/costsize.c 33 additions, 1 deletionsrc/backend/optimizer/path/costsize.c
- src/backend/optimizer/plan/createplan.c 16 additions, 3 deletionssrc/backend/optimizer/plan/createplan.c
- src/backend/optimizer/util/pathnode.c 2 additions, 4 deletionssrc/backend/optimizer/util/pathnode.c
- src/include/optimizer/cost.h 2 additions, 1 deletionsrc/include/optimizer/cost.h
Loading
Please register or sign in to comment