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

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

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Date: 2010-02-10 04:24:55
Message-ID: 20100210132455.47F4.52131E4D@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

> 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?

I think --single-transaction is useful to restore data into non-empty
databases. A normal restore ignores errors, but it might make database
inconsistent state. So, we'd better keep --single-transaction option
to support all-or-nothing restore.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center



In response to

pgsql-hackers by date

Next:From: Takahiro ItagakiDate: 2010-02-10 04:48:55
Subject: pg_restore --single-transaction and --clean
Previous:From: Tom LaneDate: 2010-02-10 04:19:04
Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore

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