Re: speeding up planning with partitions

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: speeding up planning with partitions
Date: 2019-01-21 09:01:39
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2019/01/17 11:17, Amit Langote wrote:
> I have rebased the patches. Other than rebasing, I've squashed the patch
> to add inh_root_parent field to RelOptInfo which contained no other code
> changes to use that field into the patch that contains changes to start
> using it. Updated the commit message of lazy-partition-initialization
> patch to be accurate (it contained old details that have changed since I
> first wrote that commit message).

Rebased again due to 8d8dcead1295.


Attachment Content-Type Size
v16-0001-Overhaul-inheritance-update-delete-planning.patch text/plain 75.6 KB
v16-0002-Lazy-creation-of-RTEs-for-inheritance-children.patch text/plain 97.0 KB
v16-0003-Teach-planner-to-only-process-unpruned-partition.patch text/plain 6.8 KB
v16-0004-Do-not-lock-all-partitions-at-the-beginning.patch text/plain 1.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-01-21 09:14:53 Re: Allowing extensions to find out the OIDs of their member objects
Previous Message Etsuro Fujita 2019-01-21 08:56:45 Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0