| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Robinson <robinson(at)netrinsics(dot)com> |
| Cc: | pgsql-hackers(at)hub(dot)org |
| Subject: | Re: [HACKERS] fatal copy in/out error (6.5.3) |
| Date: | 2000-01-24 17:34:19 |
| Message-ID: | 25765.948735259@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> This looks to me like something is deciding that \217 must be the
>> start of a 3-byte multibyte character... in which case, it should have
>> appeared that way in your database, I think.
> That would be very weird, if true. \217 is certainly not the beginning of
> a UTF-8 three-byte sequence, and EUC doesn't have three-byte codes.
Hmm. And I don't suppose it's real likely that \217 is a one-byte code
and \210 starts a two-byte code?
I'm out of my depth here --- it seems this is almost certainly a
MULTIBYTE issue, but I know very little about MULTIBYTE. I'm going
to punt and hope some of our MULTIBYTE experts pick it up.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henry B. Hotz | 2000-01-24 17:46:40 | Re: [HACKERS] Some notes on optimizer cost estimates |
| Previous Message | Peter Mount | 2000-01-24 17:33:58 | Re: [HACKERS] Proposed change to the JDBC driver |