Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Date
Msg-id 7513.1265773608@sss.pgh.pa.us
Whole thread Raw
In response to TRUNCATE+COPY optimization and --jobs=1 in pg_restore  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
List pgsql-hackers
Tree view 
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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CVS checkout source code for different branches
Next
From: M Z
Date:
Subject: Re: CVS checkout source code for different branches