Re: Bulkloading using COPY - ignore duplicates?

Tom Lane wrote:
> > How about for TODO:
> >     * Allow COPY to report error lines and continue; requires
> >     nested transactions;  optionally allow error codes to be specified
> 
> Okay, that seems reasonable.

Good.  Now that I think of it, nested transactions don't seem required. 
We already allow pg_dump to dump a database using INSERTs, and we don't
put those inserts in a single transaction when we load them:CREATE TABLE "test" (        "x" integer);INSERT INTO
"test"VALUES (1);INSERT INTO "test" VALUES (2);
 

Should we be wrapping these INSERTs in a transaction?  Can we do COPY
with each row being its own transaction?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026