| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Windows and locales and UTF-8 (oh my) |
| Date: | 2007-10-15 16:55:24 |
| Message-ID: | 47139B7C.1020908@hagander.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>>>> On Sat, Oct 06, 2007 at 01:53:31PM -0400, Tom Lane wrote:
>>>>> I am thinking that Dave's discovery explains some previously unsolved
>>>>> bug reports, such as
>>>>> http://archives.postgresql.org/pgsql-bugs/2007-05/msg00260.php
>> ...
>> And given that, do we even nede to special-case lc_ctype_is_c() at all? If
>> we never pass in a .65001 locale (which we don't, because it fails)?
>
> 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.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-15 17:17:59 | Re: Windows and locales and UTF-8 (oh my) |
| Previous Message | Tom Lane | 2007-10-15 16:18:41 | Re: Windows and locales and UTF-8 (oh my) |