| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Emmanuel Cecchet <manu(at)asterdata(dot)com>, Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY enhancements |
| Date: | 2009-10-08 08:42:09 |
| Message-ID: | 87vdiqgtum.fsf@hi-media-techno.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> What's really bad about this is that a flag called "error_logging" is
> actually changing the behavior of the command in a way that is far
> more dramatic than (and doesn't actually have much to do with) error
> logging. It's actually making a COPY command succeed that would
> otherwise have failed. That's not just a logging change.
That's what has been asked for, a COPY that is able to load the good
rows in the presence of bad rows. I'd rather change the option name than
the behavior. Pretty please.
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2009-10-08 10:22:03 | Re: Review of "SQLDA support for ECPG" |
| Previous Message | Dimitri Fontaine | 2009-10-08 08:34:51 | Re: Concurrency testing |