| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | stark(at)mit(dot)edu, jakob(at)eggerapps(dot)at, pgsql-hackers(at)postgresql(dot)org, tobias(dot)bussmann(at)scnat(dot)ch, girgen(at)pingpong(dot)net, magnus(at)hagander(dot)net, geoff(dot)montee(at)gmail(dot)com, dpage(at)postgresql(dot)org |
| Subject: | Re: [pgsql-packagers] Palle Girgensohn's ICU patch |
| Date: | 2014-11-27 23:49:14 |
| Message-ID: | 20141128.084914.360019478169807346.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Another issue is that (AFAIK) ICU doesn't support any non-Unicode
> encodings, which means that a build supporting *only* ICU collations is a
> nonstarter IMO. So we really need a way to deal with both system and ICU
> collations, and treating the latter as a separate subset of pg_collation
> seems like a decent way to do that. (ISTR some discussion about forcibly
> converting strings in other encodings to Unicode to compare them, but
> I sure don't want to do that. I think it'd be saner just to mark the
> ICU collations as only compatible with UTF8 database encoding.)
+1. Forcing only Unicode collation is totally unacceptable.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Barwick | 2014-11-28 02:20:26 | Re: pg_regress and --dbname option / multiple databases |
| Previous Message | Peter Geoghegan | 2014-11-27 23:24:40 | Re: [pgsql-packagers] Palle Girgensohn's ICU patch |