From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | PgSQL Novice ML <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: skipping records with duplicate key during COPY |
Date: | 2002-12-19 01:08:50 |
Message-ID: | 1040260130.28774.97.camel@haggis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, 2002-12-18 at 13:16, Devinder K Rajput wrote:
> Hi,
> I am using COPY command to load a data table. When I try to
> insert a record with a duplicate key, I get the error message "cannot
> insert a duplicate key into unique index" and no data is loaded into
> the table. I know that this is the way the COPY command works. Now,
> is there a way in which I can load a table and if duplicate records do
> come up, write them to an error file, but still load the other good
> records into the table? *I think* one of accomplishing this is by
> performing inserts of individual records, but that would be very slow.
> any suggestions?
Any method of inserting records where there is a unique index will
be slow, since the index must be checked and populated.
Your idea of doing individual inserts (via C, Python or Perl) is
a valid one, for the exact reason you state, and because input
data is not always in COPY format...
--
+---------------------------------------------------------------+
| Ron Johnson, Jr. mailto:ron(dot)l(dot)johnson(at)cox(dot)net |
| Jefferson, LA USA http://members.cox.net/ron.l.johnson |
| |
| "My advice to you is to get married: If you find a good wife, |
| you will be happy; if not, you will become a philosopher." |
| Socrates |
+---------------------------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Ludwig Lim | 2002-12-19 02:29:13 | Re: skipping records with duplicate key during COPY |
Previous Message | Tom Lane | 2002-12-18 23:58:24 | Re: Reserved Word |