Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Date
Msg-id 4B723280.5010106@dunslane.net
Whole thread Raw
In response to Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
List pgsql-hackers

Tom Lane wrote:
> Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp> writes:
>   
>> We have an optimization to bulkload date in pg_restore, but the code
>> only works in parallel restore (--jobs >= 2). Why don't we do the
>> same optimization in the serial restore (--jobs = 1) ?
>>     
>
> The code is only trying to substitute for something you can't have
> in parallel restore, ie --single-transaction.
>
>             
>   

Exactly. IIRC that's why --single-transaction was introduced in the 
first place.

Takahiro-san is suggesting there is a case for doing the optimisation in 
non-parallel mode. But if we do that, is there still a case for 
--single-transaction?

cheers

andrew


pgsql-hackers by date:

Previous
From: Takahiro Itagaki
Date:
Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Next
From: Tom Lane
Date:
Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore