| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | songhe(at)optonline(dot)net |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Sorting Chinese data in Postgresql 7.3.1 |
| Date: | 2003-01-27 04:06:03 |
| Message-ID: | 20030127.130603.15268926.t-ishii@sra.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I tried initdb -E EUC_CN --no-locale and tested "order by" with the same
> Chinese data, I got the same result: the "order by" clause does not have
> any effect. The locale on my Redhat Linux 8.0 is en_US.UTF-8.
>
> By the way, the manual page for initdb does not show an option
> --no-locale.
That's a bug with the man page. Try initdb --help to find the option.
> Could you point me to the source codes where I can pin down
> this?
No idea at this point. What about the results of following SQL?
SELECT 'chinese char1'::text > 'chinese char2'::text;
Do you get same result for any Chinese (EUC_CN) characters?
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-27 04:18:31 | Re: New hashed IN code ignores distinctiveness of subquery |
| Previous Message | Bradley Baetz | 2003-01-27 03:22:57 | Re: New hashed IN code ignores distinctiveness of subquery |