Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> When a TIMESTAMP, TIME, or INTERVAL precision is specified larger than our
>> implementation limits, do not issue an ERROR; instead issue a NOTICE and use
>> the max supported value. Per pgsql-general discussion of 28-Apr, this is
>> needed to allow easy porting from pre-7.3 releases where the limits were
>> higher.
> I'm not happy with this change. If someone explicitly put in a higher
> limit in his old applications, he expressed that he needed it, so he needs
> to see an error and adjust his applications. (Or he didn't know what he
> was doing, but we don't cater to those people.)
The person who actually ran into the situation objected to getting an
error; he felt the system ought to do the best it could with his dump
file. You could argue this either way, certainly, but our past practice
has been to try not to error out when loading a dump.
regards, tom lane