pgsql: cost_agg really ought to charge something per output tuple; else - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: cost_agg really ought to charge something per output tuple; else
Date
Msg-id 20050827223700.B5A6DD7C8B@svr1.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Change the division of labor between grouping_planner and
Next
From: jwp@pgfoundry.org (James William Pye)
Date:
Subject: python - pq: Feature cutting.