Re: when COPY violates Primary Keys

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Chris <dmagick(at)gmail(dot)com>
Cc: Joao Ferreira gmail <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: when COPY violates Primary Keys
Date: 2008-10-10 00:04:04
Message-ID: 20081010085843.9944.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Chris <dmagick(at)gmail(dot)com> wrote:

> Joao Ferreira gmail wrote:
> > in case the COPY of a register causes a primary key (or UNIQUE, or FK)
> > violation does the psql restore command try to continue the operation
> > until it has parsed the whole dump, or does it abort on the first
> > violation ?
>
> Copy is all or nothing. It'll abort as soon as a violation happens.
>
> the bulkloader on pgfoundry (http://pgfoundry.org/projects/pgbulkload/)
> can apparently handle this for you...

No, pg_bulkload is all or nothing for constraints violations.
Please use pgloader (http://pgfoundry.org/projects/pgloader/)
for the purpose.

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Wirt 2008-10-10 05:02:24 Re: [Pkg-postgresql-public] Postgres major version support policy on Debian
Previous Message Chris 2008-10-09 23:43:45 Re: when COPY violates Primary Keys