Re: [HACKERS] COPY

Theo Kramer <theo@flame.co.za> writes:
> I've been doing some big imports using COPY. Problem I have is COPY
> aborting if a field could not be parsed. What's the feeling about
> changing the behaviour so it does not abort, yet writes the offending line
> number to the error log and continues with the next line?

I can think of situations where you'd want it either way.  (For example,
in a pg_dump restore script I'd sure want big red warning flags if there
were any problems, not a piddly little message in the postmaster log...)

How about creating a SET variable that chooses either the above behavior
or the existing one?

If that seems acceptable all 'round, we can start arguing about which
way ought to be the default ;-)
        regards, tom lane