Re: Unicode license compatibility with PostgreSQL license - Mailing list pgsql-general

From Haribabu Kommi
Subject Re: Unicode license compatibility with PostgreSQL license
Date
Msg-id CAJrrPGfPEE3F=bC15WhVSzH0hqb-ncF=J3UD9eMD62-Oa=TRuA@mail.gmail.com
Whole thread Raw
In response to Re: Unicode license compatibility with PostgreSQL license  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
List pgsql-general
On Fri, Mar 20, 2015 at 5:54 AM, Peter Geoghegan
<peter.geoghegan86@gmail.com> wrote:
> On Wed, Mar 18, 2015 at 11:03 PM, Haribabu Kommi
> <kommi.haribabu@gmail.com> wrote:
>> For our next set of development activities in PostgreSQL, we want to
>> use the Unicode organization code with PostgreSQL to open source that
>> feature. Is the Unicode license is compatible with PostgreSQL.
>
> Do you mean that you'd like to add ICU support? I think that would be
> extremely interesting, FWIW. The stability of ICU collations would be
> quite helpful from a number of different perspective. One of which is
> that having a contract about the stability of strxfrm()-style binary
> keys would allow me to make text abbreviated keys exploited in the
> internal pages of B-Tree indexes, to greatly reduce cache misses with
> index scans on text attributes. This general technique already been
> very effective with sorting [1], but it feels likely that we'll need
> ICU to make the abbreviation technique useful for indexes.
>
> [1] http://pgeoghegan.blogspot.com/2015/01/abbreviated-keys-exploiting-locality-to.html

Hi All,

Thanks for the information.
we are just evaluating some conversion algorithms to convert from
UTF32/16 to UTF8 and vice versa.

Regards,
Hari Babu
Fujitsu Australia


pgsql-general by date:

Previous
From: Matija Lesar
Date:
Subject: Re: Unexpected array_remove results
Next
From: Daniel Caldeweyher
Date:
Subject: create table if not exists xx AS select ...