Robert Haas wrote: > Each of those features deserves a separate discussion to decide > whether we want it and how best to implement it. Personally, I think > we should skip (C), at least as a starting point. Instead of logging > to a table, I think we should consider making COPY return the tuples > indicating the error as a query result, the same way EXPLAIN returns > the query plan. It looks like this would eliminate the need for at > least three of the new COPY options without losing much functionality.
Can we capture EXPLAIN output into a table? If so, can the COPY error output be sent to a table so we don't need to add this functionality to COPY specifically? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
