| From: | "Joolz" <joolz(at)arbodienst-limburg(dot)nl> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | unique problem |
| Date: | 2004-11-01 15:13:43 |
| Message-ID: | 45568.10.0.4.254.1099322023.squirrel@webmail.arbodienst-limburg.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi everyone,
When importing a bunch of data (> 85000 rows) I get an error I can't
explain. The table into which I'm importing has a unique clause on
(code, bedrijf). The rows in the source-table are unique in this
aspect, yet when I do the import I get this "ERROR: duplicate key
violates unique constraint "werknemer_bedrijf_key".
I checked the sourcetable a number of times, even COPYd the relevant
columns to a textfile and did `uniq -d` and `uniq -D` (nothing
non-unique found), tried to delete out non-unique rows (again
nothing found).
Is there a bug in the UNIQUE behaviour? I'm running postgresql
7.4.5-2 (from backports) on a debian stable server. Is there any way
I can DEFER the unique clause, or remove it and put it back later?
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2004-11-01 15:16:24 | Re: Reasoning behind process instead of thread based |
| Previous Message | Michael Fuhr | 2004-11-01 14:59:46 | Re: logging queries and time used |