| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
| Cc: | Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY enhancements |
| Date: | 2009-10-07 16:25:28 |
| Message-ID: | 603c8f070910070925n1719c38aj7c589a909db2eb16@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 7, 2009 at 11:45 AM, Emmanuel Cecchet <manu(at)asterdata(dot)com> wrote:
> You are suggesting then that it is the COPY command that aborts the
> transaction. That would only happen if you had set a limit on the number of
> errors that you want to accept in a COPY command (in which case you know
> that there is something really wrong with your input file and you don't want
> the server to process that file).
But I still want my log even if the COPY bombs out. I want to report
the first group of errors back to my user...
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcelo Costa | 2009-10-07 16:38:37 | Re: Feature Suggestion: PL/Js |
| Previous Message | David E. Wheeler | 2009-10-07 16:18:57 | Re: Feature Suggestion: PL/Js |