| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
| Subject: | Re: Evaluate expression at planning time for two more cases |
| Date: | 2020-11-16 11:05:03 |
| Message-ID: | 160552470322.32482.1367621091798274540.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thank you for working on this!
I got slightly into this patch. I can be wrong, but my opinion is that planner/optimizer-related changes are not without dangers generally. So anyway, they should be justified by performance increase, or the previous behavior should be considered totally wrong. Patching the thing which is just a little sub-optimal seems for me seems not necessary.
So it would be very good to see measurements of a performance gain from this patch. And also I think tests with partitioned and inherited relations for demonstration of the right work in the cases discussed in the thread should be a must-do for this patch.
--
Best regards,
Pavel Borisov
Postgres Professional: http://postgrespro.com
The new status of this patch is: Waiting on Author
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2020-11-16 11:31:29 | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Previous Message | torikoshia | 2020-11-16 10:58:55 | Re: Get memory contexts of an arbitrary backend process |