> 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
