Re: tsearch in core patch

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Hannu Krosing <hannu(at)skype(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tsearch in core patch
Date: 2007-06-22 15:03:28
Message-ID: 467BE4C0.2030008@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> I very much doubt that the different spanishes are any different in the
>> stemming rules, so there's no need for es_ES, es_PE, es_AR, es_CL etc;
>> but in the case of portuguese I'm not so sure. Maybe there are other
>> examples (like chinese, but I'm not sure how useful is tsearch for
>> chinese).
>
>> And the .ISO8859-1 part you don't need at all if you accept that the
>> files are UTF8 by design, as Tom proposed.
>
> Also, the problem we're dealing with here is mainly lack of
> standardization of the encoding part of locale names. AFAIK, just about
> everybody agrees on "es_ES", "ru_RU", etc; it's the part that comes
> after that (if any) that is not too consistent across platforms.

That may have been true until we started supporting Windows...
Swedish_Sweden.1252 is what I get on my machine, for example. Principle
is the same, but values certainly aren't.

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-06-22 15:06:30 Re: Worries about delayed-commit semantics
Previous Message Oleg Bartunov 2007-06-22 15:02:37 Re: tsearch in core patch