Re: Patch for collation using ICU

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Hansen" <john(at)geeknet(dot)com(dot)au>
Cc: "Palle Girgensohn" <girgen(at)pingpong(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch for collation using ICU
Date: 2005-05-07 23:41:11
Message-ID: 6501.1115509271@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
> Btw, I had been planning to propose replacing every single one of the
> built in charset conversion functions with calls to ICU (thus making
> pg _depend_ on ICU),

I find that fairly unacceptable ... especially given the licensing
questions, but in any case.

It might be OK to rip out the existing conversion support and say
that *if* you want encoding conversion, you have to use ICU. But
I don't want to be told you cannot build PG without ICU period.

The 3.2 vs 2.8 business is disturbing also; specifically, I don't
think we get to require 3.2 on a platform where 2.8 is installed.
People just aren't going to hold still for that, even assuming
that ICU supports installing both versions at once, which isn't
clear to me at the moment ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2005-05-07 23:44:56 Fix PID file location?
Previous Message Neil Conway 2005-05-07 23:22:55 Re: pl/pgsql enabled by default