| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-09 16:14:00 |
| Message-ID: | 25107.1189354440@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-09 16:28:14 | Are we done with sync-commit-defaults-to-off patch? |
| Previous Message | Andrew Dunstan | 2007-09-09 15:56:27 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-09-09 17:18:23 | Re: invalidly encoded strings |
| Previous Message | Andrew Dunstan | 2007-09-09 15:56:27 | Re: invalidly encoded strings |