Re: Parallel INSERT (INTO ... SELECT ...)

From: Greg Nancarrow <gregn4422(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)fujitsu(dot)com>, "Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>
Subject: Re: Parallel INSERT (INTO ... SELECT ...)
Date: 2021-02-19 01:25:56
Message-ID: CAJcOf-e9Q+XC2r7pJgaDHCOw92DQX3c7pu9FTMSZRzNSq6Sz9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Posting a new version of the patches, with the following updates:
- Moved the update of glob->relationOIDs (i.e. addition of partition
OIDs that plan depends on, resulting from parallel-safety checks) from
within max_parallel_hazard() to set_plan_references().
- Added an extra test for partition plan-cache invalidation.
- Simplified query_has_modifying_cte() temporary bug-fix.
- Added a comment explaining why parallel-safety of partition column
defaults is not checked.
- Minor simplification: hasSubQuery return to is_parallel_possible_for_modify().

Regards,
Greg Nancarrow
Fujitsu Australia

Attachment Content-Type Size
v18-0002-Parallel-SELECT-for-INSERT-INTO-.-SELECT-tests-and-doc.patch application/octet-stream 66.3 KB
v18-0003-Enable-parallel-INSERT-and-or-SELECT-for-INSERT-INTO.patch application/octet-stream 44.4 KB
v18-0001-Enable-parallel-SELECT-for-INSERT-INTO-.-SELECT.patch application/octet-stream 29.4 KB
v18-0004-Parallel-INSERT-and-or-SELECT-for-INSERT-INTO-tests-and-doc.patch application/octet-stream 22.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-02-19 01:54:05 Re: Printing LSN made easy
Previous Message Bossart, Nathan 2021-02-19 01:18:30 Re: documentation fix for SET ROLE