Re: The dangers of streaming across versions of glibc: A cautionary tale

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: peter(dot)geoghegan86(at)gmail(dot)com
Cc: bruce(at)momjian(dot)us, mkelly(at)tripadvisor(dot)com, pgsql-general(at)postgresql(dot)org, mspilich(at)tripadvisor(dot)com
Subject: Re: The dangers of streaming across versions of glibc: A cautionary tale
Date: 2014-08-07 01:30:48
Message-ID: 20140807.103048.1016702529143996447.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Over time, collation order will vary: there may be fixes needed as
> more information becomes available about languages; there may be new
> government or industry standards for the language that require
> changes; and finally, new characters added to the Unicode Standard
> will interleave with the previously-defined ones. This means that
> collations must be carefully versioned.

Another idea could be having our own collation data to isolate any
changes from outside world. I vaguley recall this had been discussed
before.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2014-08-07 01:46:49 Re: The dangers of streaming across versions of glibc: A cautionary tale
Previous Message Phoenix Kiula 2014-08-07 01:21:17 Need help in tuning