From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unicode license compatibility with PostgreSQL license |
Date: | 2015-03-22 23:59:34 |
Message-ID: | CAJrrPGfPEE3F=bC15WhVSzH0hqb-ncF=J3UD9eMD62-Oa=TRuA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Mar 20, 2015 at 5:54 AM, Peter Geoghegan
<peter(dot)geoghegan86(at)gmail(dot)com> wrote:
> On Wed, Mar 18, 2015 at 11:03 PM, Haribabu Kommi
> <kommi(dot)haribabu(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Caldeweyher | 2015-03-23 01:28:31 | create table if not exists xx AS select ... |
Previous Message | Matija Lesar | 2015-03-21 17:10:04 | Re: Unexpected array_remove results |