From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, <ZeugswetterA(at)spardat(dot)at>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <phede-ml(at)islande(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unicode combining characters |
Date: | 2001-10-03 20:46:55 |
Message-ID: | Pine.LNX.4.30.0110031944550.635-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane writes:
> In the meantime, we still have the question of whether to enable
> multibyte in the default configuration.
This would make more sense if all of multibyte, locale, and NLS became
defaults in one release. I haven't quite sold people in the second item
yet, although I have a design how to do that (see below). And the third,
well who knows...
Perhaps we could make it a release goal for 7.3 to
* Optimize i18n stuff to have a minimal performance penalty when it's not
used. (locale=C etc.)
* Make i18n stuff sufficiently well-behaved to make it the default.
(Especially, add initdb options and GUC parameters to set the locale.
Don't rely on environment variables -- too complicated.)
Meanwhile, quadratic performance penalties (or so it seems) for LIKE
expressions aren't exactly a "minor" problem.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-10-03 20:56:28 | Re: COMMENT ON |
Previous Message | Tom Lane | 2001-10-03 20:44:32 | Re: Unicode combining characters |
From | Date | Subject | |
---|---|---|---|
Next Message | Paul A Vixie | 2001-10-03 20:53:58 | Re: IPv6 Support for INET/CIDR types. |
Previous Message | Tom Lane | 2001-10-03 20:44:32 | Re: Unicode combining characters |