| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: using Core Foundation locale functions |
| Date: | 2014-12-03 05:52:02 |
| Message-ID: | 20141203055202.GA1573747@tornado.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 28, 2014 at 11:43:28AM -0500, Peter Eisentraut wrote:
> In light of the recent discussions about using ICU on OS X, I looked
> into the Core Foundation locale functions (Core Foundation = traditional
> Mac API in OS X, as opposed to the Unix/POSIX APIs).
>
> Attached is a proof of concept patch that just about works for the
> sorting aspects. (The ctype aspects aren't there yet and will crash,
> but they could be done similarly.) It passes an appropriately adjusted
> collate.linux.utf8 test, meaning that it does produce language-aware
> sort orders that are equivalent to what glibc produces.
>
> At the moment, this is probably just an experiment that shows where
> refactoring and better abstractions might be suitable if we want to
> support multiple locale libraries. If we want to pursue ICU, I think
> this could be a useful third option.
Does this make the backend multi-threaded?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-12-03 06:07:10 | Re: using Core Foundation locale functions |
| Previous Message | Peter Eisentraut | 2014-12-03 04:56:55 | pgsql: Fix whitespace |