pgsql: cost_agg really ought to charge something per output tuple; else

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: cost_agg really ought to charge something per output tuple; else
Date: 2005-08-27 22:37:00
Message-ID: 20050827223700.B5A6DD7C8B@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
cost_agg really ought to charge something per output tuple; else there
are cases where it appears to have zero run cost.

Modified Files:
--------------
pgsql/src/backend/optimizer/path:
costsize.c (r1.146 -> r1.147)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/costsize.c.diff?r1=1.146&r2=1.147)

Browse pgsql-committers by date

  From Date Subject
Next Message James William Pye 2005-08-27 23:55:54 python - pq: Feature cutting.
Previous Message Tom Lane 2005-08-27 22:13:44 pgsql: Change the division of labor between grouping_planner and