Re: COPY enhancements

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Emmanuel Cecchet <manu(at)asterdata(dot)com>
Cc: Selena Deckelmann <selenamarie(at)gmail(dot)com>, Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY enhancements
Date: 2009-10-05 17:01:20
Message-ID: 4ACA2660.9080600@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Emmanuel,

> I think that this was the original idea but we should probably rollback
> the error logging if the command has been rolled back. It might be more
> consistent to use the same hi_options as the copy command. Any idea what
> would be best?

Well, if we're logging to a file, you wouldn't be *able* to roll them
back. Also, presumbly, if you abort a COPY because of errors, you
probably want to keep the errors around for later analysis. No?

--Josh Berkus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-10-05 17:17:32 Re: Rules: A Modest Proposal
Previous Message Stephen Frost 2009-10-05 16:28:55 Re: Rules: A Modest Proposal