Re: tsearch in core patch - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: tsearch in core patch
Date
Msg-id 467BE4C0.2030008@hagander.net
Whole thread Raw
In response to Re: tsearch in core patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tsearch in core patch
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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



pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: tsearch in core patch
Next
From: Bruce Momjian
Date:
Subject: Re: Worries about delayed-commit semantics