| From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrzej Barszcz <abusinf(at)gmail(dot)com> |
| Subject: | Re: function calls optimization |
| Date: | 2019-11-21 01:05:14 |
| Message-ID: | CAKU4AWqmcGQiwSXbQ_zJTZrj+yH_LDqo+BSWYk_qbOQEnjFrZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 31, 2019 at 11:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> Possibly this could be finessed by only trying to find duplicates of
> functions that have high cost estimates. Not sure how high is high
> enough.
can we just add a flag on pg_proc to show if the cost is high or not, if
user are not happy with that, they can change it by updating the value?
based on that most of the function call cost are low, this way may be
helpful for the searching of duplicate expressions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-11-21 01:07:03 | Re: checkpointer: PANIC: could not fsync file: No such file or directory |
| Previous Message | Andy Fan | 2019-11-21 00:30:51 | Re: why doesn't optimizer can pull up where a > ( ... ) |