| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bulkloading using COPY - ignore duplicates? |
| Date: | 2001-10-02 22:13:46 |
| Message-ID: | Pine.LNX.4.30.0110022311470.796-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> It occurs to me that skip-the-insert might be a useful option for
> INSERTs that detect a unique-key conflict, not only for COPY. (Cf.
> the regular discussions we see on whether to do INSERT first or
> UPDATE first when the key might already exist.) Maybe a SET variable
> that applies to all forms of insertion would be appropriate.
What we need is:
1. Make errors not abort the transaction.
2. Error codes
Then you can make your client deal with this in which ever way you want,
at least for single-value inserts.
However, it seems to me that COPY ignoring duplicates can easily be done
by preprocessing the input file.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-10-02 22:14:16 | Re: Unicode combining characters |
| Previous Message | Dave Harkness | 2001-10-02 22:03:56 | Re: LOCK TABLE oddness in PLpgSQL function called via JDBC |