Robert Haas <robertmh...@gmail.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
