Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> How many datatype have this issue?
> I don't think that many do.. A number of them already check incoming
> values where it's possible for them to not be valid.
In general we do check incoming binary values to ensure minimal
validity. I think when I did timestamp_recv I was thinking it was
just like int8 or float8 (respectively), in that any bit pattern is
potentially legal; I had forgotten about the range restrictions.
I haven't looked at the details of Stephen's patch (and can't till the
archives site comes back up) but the idea is probably sound.
regards, tom lane