| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: set the cost of an aggregate function |
| Date: | 2010-02-09 04:01:53 |
| Message-ID: | 3073cc9b1002082001k7fbd40a0p168df5ae486259f4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 3, 2009 at 7:19 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> The answer is nobody got round to enhancing this yet and well considered
> proposals and subsequent patches would be welcome.
>
what is a well considered proposal in this area? the transition
function cost should be applied to every row cost (maybe multiplied to
cpu_operator_cost or cpu_tuple_cost) and the final function cost
should be applied just once, no?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Z | 2010-02-09 04:04:51 | Re: CVS checkout source code for different branches |
| Previous Message | Tom Lane | 2010-02-09 03:43:08 | Re: [CFReview] Red-Black Tree |