| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(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 14:15:31 |
| Message-ID: | 603c8f070910070715u3be478d5l1ae4e9783782dbe3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 7, 2009 at 9:12 AM, Emmanuel Cecchet <manu(at)asterdata(dot)com> wrote:
> Hi all,
>
> I think there is a misunderstanding about what the current patch is about.
> The patch includes 2 things:
> - error logging in a table for bad tuples in a COPY operation (see
> http://wiki.postgresql.org/wiki/Error_logging_in_COPY for an example; the
> error message, command and so on are automatically logged)
> - auto-partitioning in a hierarchy of child table if the COPY targets a
> parent table.
> The patch does NOT include:
> - logging errors into a file (a feature we can add later on (next commit
> fest?))
My failure to have read the patch is showing here, but it seems to me
that error logging to a table could be problematic: if the transaction
aborts, we'll lose the log. If this is in fact a problem, we should
be implementing logging to a file (or stdout) FIRST.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-10-07 14:22:02 | Re: Feature Suggestion: PL/Js |
| Previous Message | Simon Riggs | 2009-10-07 13:56:41 | Re: COPY enhancements |