| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Langote' <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: speeding up planning with partitions |
| Date: | 2018-08-30 01:45:43 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FAA4388@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Amit Langote [mailto:Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp]
> We can definitely try, but I'm not immediately sure if the further
> improvements will come from continuing to fix the planner. Maybe, the
> overhead of partitioning could be attributed to other parts of the system.
> Actually, I wrote that for patch 0002. The next patch (0003) is meant to
> fix that. So, the overhead you're seeing is even after making sure that
> only the selected partitions are locked.
Thanks for telling your thought. I understood we should find the bottleneck with profiling first.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuro Yamada | 2018-08-30 02:30:29 | Re: Fix help option of contrib/oid2name |
| Previous Message | Amit Langote | 2018-08-30 01:33:21 | Re: speeding up planning with partitions |