| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How does the tsearch configuration get selected? |
| Date: | 2007-06-15 14:43:56 |
| Message-ID: | 3582.1181918636@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Do locale names vary across operating systems?
Yes, which is the fatal flaw in the whole thing. The ru_RU part is
reasonably well standardized, but the encoding part is not. Considering
that encoding is exactly the part of it we don't care about for this
purpose (because we should look to the database encoding instead),
I think it's just going to make life harder not easier to model search
language names on locales.
I'd suggest allowing either full names ("swedish") or the standard
two-letter abbreviations ("sv"). But let's stay away from locale names.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-06-15 14:46:46 | Re: How does the tsearch configuration get selected? |
| Previous Message | Tom Lane | 2007-06-15 14:36:15 | Re: tsearch_core patch: permissions and security issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-06-15 14:46:46 | Re: How does the tsearch configuration get selected? |
| Previous Message | Teodor Sigaev | 2007-06-15 14:43:15 | Re: Tsearch vs Snowball, or what's a source file? |