#33145: postgresql90,postgresql91 improvement to Unicode support -------------------------------------------+-------------------------------- Reporter: mail_ben_schmidt@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: postgresql90,postgresql91 -------------------------------------------+-------------------------------- Because Mac OS X's POSIX locale support is flakey, PostgreSQL does not sort UTF-8 text properly (or do other character and collation-related operations properly). FreeBSD suffers from the same problem. A workaround is to patch PostgreSQL to use the ICU library (http://site .icu-project.org/) instead of the system's locale-related functions. FreeBSD have done this (http://people.freebsd.org/~girgen/postgresql- icu/README.html). PostgreSQL then works properly. I have updated the Portfiles for the postgresql90 and postgresql91 ports, and updated and added the patches to do this. There are a few deficiencies: - Autoconf now needs to be run, but the version has been changed (which isn't recommended by PostgreSQL) and is hardcoded to the version currently in MacPorts (so will break once the autoconf port moves to a new version). It would be better to make MacPorts use autoconf 2.63 (which, after all, is available as a port), and we won't have this problem. (We also won't need the uuid-related update.) - It would be good to have a better way of testing for the ICU library in ./configure rather than hardcoding in library symbols to search for that are specific to the library version (and thus will break as soon as the ICU port is updated). - ICU should perhaps be a variant (quite possibly it should be the default variant, but still, perhaps a variant is best rather than always using it). I am happy to help address these (or other) problems, but I wanted to raise the issue first, and find out what you maintainers think before proceeding any further. Hopefully we can get the patch applied upstream, too, and then MacPorts need only supply appropriate configure options and dependencies. But I think it's best to get it working with the patch in MacPorts first. -- Ticket URL: <https://trac.macports.org/ticket/33145> MacPorts <http://www.macports.org/> Ports system for Mac OS