Skip site navigation (1) Skip section navigation (2)

Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Date: 2010-02-10 03:46:48
Message-ID: 7513.1265773608@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: M ZDate: 2010-02-10 03:49:44
Subject: Re: CVS checkout source code for different branches
Previous:From: Robert HaasDate: 2010-02-10 03:43:39
Subject: Re: CVS checkout source code for different branches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group