>I think we should try to make our cost estimations more realistic in terms of cpu and io and don't try to put everything in rows as it is the case for various operators. This of course requires the VolcanoCost to be adapted.
Well. The more I revise costs, the more I incline to that opinion as well. It looks the comparison should be based on cpu+io*CPU_PER_IO. Then 'rows' becomes obsolete :-/ It seems rows duplicates rowCount metadata, thus I am inclined to hide 'rows' from toString output. Probably, toString should show cpu+io*CPU_PER_IO result. Vladimir
