Re: Collations and Replication; Next Steps - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Collations and Replication; Next Steps
Date
Msg-id 20140918.084621.1532340783089281990.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: Collations and Replication; Next Steps  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
> On Wed, Sep 17, 2014 at 3:47 PM, Tatsuo Ishii <ishii@postgresql.org> wrote:
>> I don't think we cannot achieve that because even MySQL accomplishes:-)
> 
> We've always considered it an advantage that we're consistent with the
> collations in the rest of the system. Generally speaking the fact that
> Postgres integrates with the system rather than be a separate system
> unto itself.
>
> Consider bug reports like "I've configured my system to use
> fr_FR.UTF-8 and "sort" produces output in this order why is Postgres
> producing output in a different order? Or extension authors using
> strcoll and being surprised that the module gets inconsistent data
> from the database.

I doubt it. glibc takes liberty to change the collation data release
by release, but people don't seem to complain it. Then why would
people complain the collation difference between PostgreSQL and glibc
if there's any?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Collations and Replication; Next Steps
Next
From: Robert Haas
Date:
Subject: Re: Collations and Replication; Next Steps