| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: speeding up planning with partitions |
| Date: | 2019-02-22 18:01:46 |
| Message-ID: | 20190222180146.GH28750@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Feb 23, 2019 at 02:54:35AM +0900, Amit Langote wrote:
> > On Fri, Feb 22, 2019 at 09:45:38PM +0900, Amit Langote wrote:
> > > I have updated the inheritance expansion patch.
> > >
> > > Patch 0001 rewrites optimizer/utils/inherit.c, so that it allows
> >
> > Thanks for your continued work on this.
> >
> > I applied v23 patch and imported one of our customers' schema, and ran explain
> > on a table with 210 partitions. With patch applied there are 10x fewer system
> > calls, as intended.
>
> OK, great. I guess you were running SELECT? Just in case you missed,
> the patch to improve UPDATE/DELETE scalability is no longer part of
> this patch series.
Yes, I understand the scope is reduced.
Actually, when I tested last month, I don't think I realized that UPDATE/DELETE
was included. Otherwise I would've also tested to see if it resolves the
excessive RAM use with many partitions, with the explanation given that query
is being replanned for every partition.
I set target version to v12.
https://commitfest.postgresql.org/22/1778/
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-02-22 18:03:54 | Re: Autovaccuum vs temp tables crash |
| Previous Message | Tom Lane | 2019-02-22 17:54:47 | Re: Autovaccuum vs temp tables crash |