Andrew Dunstan <andrew@dunslane.net> writes:
> Is that going to cover data coming in via COPY? and parameters for
> prepared statements?
Those should be checked already --- if not, the right fix is still to
fix it there, not in per-datatype code. I think we are OK though,
eg see "need_transcoding" logic in copy.c.
>> In SQL_ASCII I'd argue for allowing 0..255. In actual MB encodings,
>> OK with throwing error.
> I was planning on allowing up to 255 for all single byte encodings too.
OK, that sounds fine.
regards, tom lane