From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Optimizer questions |
Date: | 2016-01-06 00:13:46 |
Message-ID: | CAPpHfdvhRJo_+Xzcf5Raeiv-m13d-1dYZ_s6LrxDquR9FA0Q6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 6, 2016 at 12:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> konstantin knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> writes:
> > 1. The cost compared in grouping_planner doesn't take in account price
> of get_authorized_users - it is not changed when I am altering function
> cost. Is it correct behavior?
>
> The general problem of accounting for tlist eval cost is not handled very
> well now, but especially not with respect to the idea that different paths
> might have different tlist costs. I'm working on an upper-planner rewrite
> which should make this better, or at least make it practical to make it
> better.
>
Hmm... Besides costing it would be nice to postpone calculation of
expensive tlist functions after LIMIT.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-01-06 00:13:55 | Re: Making tab-complete.c easier to maintain |
Previous Message | Haribabu Kommi | 2016-01-05 23:14:02 | Re: Function and view to retrieve WAL receiver status |