Hello,
I reported bug #943 (I found in 7.3.2) and you checked in some change against integer overflow.
Now I upgraded to 7.3.3 and I'm not happy with this.
The exact error as I described is fixed, but I found new errors in conversion UTF-8 <-> EUC_TW and BIG5:
Copy to table (DB has UTF-8 encoding) from file:
for PGCLIENTENCODING=BIG5:
WARNING: copy: line 1, LocalToUtf: could not convert (0xf9d6) BIG5 to UTF-8. Ignored
WARNING: copy: line 2, LocalToUtf: could not convert (0xf9d7) BIG5 to UTF-8. Ignored
WARNING: copy: line 3, LocalToUtf: could not convert (0xf9d8) BIG5 to UTF-8. Ignored
WARNING: copy: line 4, LocalToUtf: could not convert (0xf9db) BIG5 to UTF-8. Ignored
for EUC_TW
WARNING: copy: line 1, LocalToUtf: could not convert (0x8ea3c3b7) EUC_TW to UTF-8. Ignored
WARNING: copy: line 2, LocalToUtf: could not convert (0x8ea3cfd0) EUC_TW to UTF-8. Ignored
WARNING: copy: line 3, LocalToUtf: could not convert (0x8ea3c4ce) EUC_TW to UTF-8. Ignored
WARNING: copy: line 4, LocalToUtf: could not convert (0x8ea3bdfe) EUC_TW to UTF-8. Ignored
Copy out to file from table (UTF-8 data):
to BIG5
WARNING: UtfToLocal: could not convert UTF-8 (0xe7a281). Ignored
WARNING: UtfToLocal: could not convert UTF-8 (0xe98ab9). Ignored
WARNING: UtfToLocal: could not convert UTF-8 (0xe8a38f). Ignored
WARNING: UtfToLocal: could not convert UTF-8 (0xe7b2a7). Ignored
to EUC_TW is ok!
Regards,
Michael
