From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'David Rowley' <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "Kato, Sho" <kato-sho(at)jp(dot)fujitsu(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: How to make partitioning scale better for larger numbers of partitions |
Date: | 2018-07-13 06:53:05 |
Message-ID: | 0A3221C70F24FB45833433255569204D1FA5002F@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: David Rowley [mailto:david(dot)rowley(at)2ndquadrant(dot)com]
> > David has submitted multiple patches for PG 12, one of which speeds up
> pruning of UPDATE/DELETE (I couldn't find it in the current CF, though.)
> What challenges are there for future versions, and which of them are being
> addressed by patches in progress for PG 12, and which issues are untouched?
>
> I've not submitted that for PG12 yet. I had other ideas about just
> getting rid of the inheritance planner altogether, but so far don't
> have a patch for that. Still uncertain if there are any huge blockers
> to that either.
Sorry, I seem to have misunderstood something.
By the way, what do you think is the "ideal and should-be-feasible" goal and the "realistic" goal we can reach in the near future (e.g. PG 12)? Say,
* Planning and execution time is O(log n), where n is the number of partitions
* Planning time is O(log n), execution time is O(1)
* Planning and execution time is O(1), where n is the number of partitions
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Ideriha, Takeshi | 2018-07-13 07:03:43 | RE: Global shared meta cache |
Previous Message | Amit Langote | 2018-07-13 06:28:52 | Re: How to make partitioning scale better for larger numbers of partitions |