| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: Errors in our encoding conversion tables |
| Date: | 2015-11-27 16:01:36 |
| Message-ID: | 17226.1448640096@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> I agree with your proposed fix, the only thing that makes me feel uncomfortable
> is that you get error messages like:
> ERROR: character with byte sequence 0x96 in encoding "WIN1250" has no equivalent in encoding "MULE_INTERNAL"
Hm, yeah. It's pretty silly that this code uses a double conversion when
it has a table that would work fine for a direct conversion, anyway. But
I think improving that is a separate question, especially since the above
behavior occurred already for a few code points.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2015-11-27 16:15:47 | Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..) |
| Previous Message | Dmitry Ivanov | 2015-11-27 15:52:59 | [PROPOSAL] Backup and recovery of pg_statistic |