"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> It is in the release notes. I'm not sure why the behaviour was changed
> (other than it really is bad behaviour).
I think someone exhibited a case where COPY behavior was really
confusing because it was silently accepting an empty string for an int
field, instead of giving an error. Since the behavior seemed obviously
bogus anyway, we were finally motivated to change it.
regards, tom lane