Re: Bulkloading using COPY - ignore duplicates?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:15:04
Message-ID: 200201032115.g03LF4j22668@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mikheev, Vadim wrote:
> > > 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.

OK, updated TODO to prefer savepoints term.

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-01-03 21:33:02 postgresql.conf syntax
Previous Message Mikheev, Vadim 2002-01-03 21:11:34 Re: Bulkloading using COPY - ignore duplicates?