| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Practical error logging for very large COPY statements |
| Date: | 2005-11-22 00:38:35 |
| Message-ID: | 4382688B.7050700@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
>
>
>>What I'd like to do is add an ERRORTABLE clause to COPY. The main
>>problem is how we detect a duplicate row violation, yet prevent it from
>>aborting the transaction.
>>
>>
>
>If this only solves the problem of duplicate keys, and not any other
>kind of COPY error, it's not going to be much of an advance.
>
>
Yeah, and I see errors from bad data as often as from violating
constraints. Maybe the best way if we do something like this would be to
have the error table contain a single text, or maybe bytea, field which
contained the raw offending input line.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-11-22 00:50:48 | Re: [HACKERS] Should libedit be preferred to libreadline? |
| Previous Message | Alvaro Herrera | 2005-11-22 00:33:16 | Re: PostgreSQL 8.1.0 catalog corruption |