Re: speeding up planning with partitions - Mailing list pgsql-hackers

From Amit Langote
Subject Re: speeding up planning with partitions
Date
Msg-id 9feacaf6-ddb3-96dd-5b98-df5e927b1439@lab.ntt.co.jp
Whole thread Raw
In response to RE: speeding up planning with partitions  ("Imai, Yoshikazu" <imai.yoshikazu@jp.fujitsu.com>)
Responses RE: speeding up planning with partitions
List pgsql-hackers
Imai-san,

On 2019/03/15 9:33, Imai, Yoshikazu wrote:
> On Thu, Mar 14, 2019 at 9:04 AM, Amit Langote wrote:
>>> * In inheritance_planner(), we do ChangeVarNodes() only for orig_rtable,
>> so the codes concatenating lists of append_rel_list may be able to be
>> moved before doing ChangeVarNodes() and then the codes concatenating
>> lists of rowmarks, rtable and append_rel_list can be in one block (or
>> one bunch).
>>
>> Yeah, perhaps.  I'll check.

I'm inclined to add source_appinfos to subroot->append_rel_list after
finishing the ChangeVarNodes(subroot->append_rel_list) step, because if
there are many entries in source_appinfos that would unnecessarily make
ChangeVarNodes take longer.

>> On 2019/03/14 17:35, Imai, Yoshikazu wrote:> Amit-san,
>>> I have done code review of v31 patches from 0004 to 0008.
>>>
>>> 0004:
>>> * s/childern/children
>>
>> Will fix.

Fixed.

I've attached updated patches.  In the new version, I've moved some code
from 0004 to 0005 patch, so as to avoid mixing unrelated modifications in
one patch.  Especially, orig_rtable now only appears after applying 0005.

I appreciate your continued interest in these patches.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade version checking questions
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade version checking questions