| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: COPY enhancements |
| Date: | 2009-09-12 07:12:23 |
| Message-ID: | 4AAB49D7.50002@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
>> The user-defined table for rejects is obviously exclusive of the system
>> one, either of those would be fine from my perspective.
>
> I've been thinking about it, and can't come up with a really strong case
> for wanting a user-defined table if we settle the issue of having a
> strong key for pg_copy_errors. Do you have one?
A user-defined error callback function would be nice. The function could
insert the erroneous rows to a table, write to a file, print a warning,
perform further checks, or whatever. This assumes that errors are seldom
enough that the error-path is not performance-critical.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-09-12 08:22:01 | Re: COPY enhancements |
| Previous Message | Heikki Linnakangas | 2009-09-12 07:07:13 | Re: COPY enhancements |