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

From: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
To: "tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>
Cc: 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Antonin Houska <ah(at)cybertec(dot)at>
Subject: RE: Parallel INSERT (INTO ... SELECT ...)
Date: 2021-01-18 00:57:19
Message-ID: OSBPR01MB29823755AC1E0A21D4CD736DFEA40@OSBPR01MB2982.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Tang-san,

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> Can we test cases when we have few rows in the Select table (say 1000)
> and there 500 or 1000 partitions. In that case, we won't select
> parallelism but we have to pay the price of checking parallel-safety
> of all partitions. Can you check this with 100, 200, 500, 1000
> partitions table?

I also wanted to see such an extreme(?) case. The 1,000 rows is not the count per partition but the total count of all partitions.e.g., when # of partitions is 100, # of rows per partition is 10.

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2021-01-18 01:41:54 Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Previous Message Robert Haas 2021-01-18 00:50:13 Re: Key management with tests