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(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

• Re: Bulkloading using COPY - ignore duplicates? at 2002-01-03 00:05:17 from Tom Lane

Responses

• Re: Bulkloading using COPY - ignore duplicates? at 2002-01-03 18:24:26 from Bruce Momjian

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2002-01-03 04:05:23
	Subject: Re: bug in join?
Previous:	From: Tatsuo Ishii	Date: 2002-01-03 01:18:25
	Subject: Re: LWLock contention: I think I understand the problem