RE: Parallel INSERT (INTO ... SELECT ...) - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: Parallel INSERT (INTO ... SELECT ...)
Date
Msg-id TYAPR01MB2990785927B213AB5FD93020FEA20@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Parallel INSERT (INTO ... SELECT ...)  ("Tang, Haiying" <tanghy.fnst@cn.fujitsu.com>)
List pgsql-hackers
From: Tang, Haiying <tanghy.fnst@cn.fujitsu.com>
> Execute EXPLAIN on Patched:
>  Insert on public.test_part  (cost=0.00..15.00 rows=0 width=0) (actual
> time=44.139..44.140 rows=0 loops=1)
>    Buffers: shared hit=1005 read=1000 dirtied=3000 written=2000
>    ->  Seq Scan on public.test_data1  (cost=0.00..15.00 rows=1000
> width=8) (actual time=0.007..0.201 rows=1000 loops=1)
>          Output: test_data1.a, test_data1.b
>          Buffers: shared hit=5

> Execute EXPLAIN on non-Patched:
>  Insert on public.test_part  (cost=0.00..15.00 rows=0 width=0) (actual
> time=72.656..72.657 rows=0 loops=1)
>    Buffers: shared hit=22075 read=1000 dirtied=3000 written=2000
>    ->  Seq Scan on public.test_data1  (cost=0.00..15.00 rows=1000
> width=8) (actual time=0.010..0.175 rows=1000 loops=1)
>          Output: test_data1.a, test_data1.b
>          Buffers: shared hit=5

I don't know if this is related to this issue, but I felt "shared hit=5" for Seq Scan is strange.  This test case reads
1,000rows from 1,000 partitions, one row per partition, so I thought the shared hit should be 1,000 in Seq Scan.  I
wonderif the 1,000 is included in Insert node?
 


Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: "Hou, Zhijie"
Date:
Subject: RE: Add Nullif case for eval_const_expressions_mutator
Next
From: Tom Lane
Date:
Subject: Re: [PATCH 1/1] Fix detection of pwritev support for OSX.