| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Windows and locales and UTF-8 (oh my) |
| Date: | 2007-10-15 17:17:59 |
| Message-ID: | 18302.1192468679@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> Hmm. If it doesn't need a special case, then we still lack an
>> explanation for the aforementioned bug report.
> From what I can tell that report doesn't tell us very much - we don't
> know server encoding, we don't know server locale, we don't even know
> client encoding. So I don't think we know anywhere *near* enough to say
> it's related to this.
In the followup we found out that he was using UTF-8 encoding:
http://archives.postgresql.org/pgsql-bugs/2007-05/msg00264.php
So while that report certainly left a great deal to be desired in terms
of precision, my gut tells me it's related. Has anyone tried to
reproduce that behavior by initdb'ing 8.2 in a suitable UTF-8-using
Windows locale?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-10-15 17:44:00 | Re: Windows and locales and UTF-8 (oh my) |
| Previous Message | Magnus Hagander | 2007-10-15 16:55:24 | Re: Windows and locales and UTF-8 (oh my) |