From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unicode license compatibility with PostgreSQL license |
Date: | 2015-03-19 18:54:32 |
Message-ID: | CAEYLb_U9d30Mm5vDuJrJSnin43vQVpxOA9dNHQ9fzCvebts_kw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
--
Regards,
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2015-03-19 19:36:25 | Re: How does one make the following psql statement sql-injection resilient? |
Previous Message | John R Pierce | 2015-03-19 18:39:57 | Re: Unicode license compatibility with PostgreSQL license |