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

Re: Bulkloading using COPY - ignore duplicates?

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jim Buttafuoco <jim(at)buttafuoco(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bulkloading using COPY - ignore duplicates?
Date: 2002-01-03 21:11:34
Message-ID: 3705826352029646A3E91C53F7189E32518469@sectorbase2.sectorbase.com (view raw or flat)
Thread:
Lists: pgsql-hackers 
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > Seems nested transactions are not required if we load
> > > each COPY line in its own transaction, like we do with
> > > INSERT from pg_dump.
> > 
> > I don't think that's an acceptable answer.  Consider
> 
> Oh, very good point.  "Requires nested transactions" added to TODO.

Also add performance issue with per-line-commit...

Also-II - there is more common name for required feature - savepoints.

Vadim

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2002-01-03 21:15:04
Subject: Re: Bulkloading using COPY - ignore duplicates?
Previous:From: Tom LaneDate: 2002-01-03 20:58:02
Subject: Re: More problem with scripts

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