| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How does the tsearch configuration get selected? |
| Date: | 2007-06-15 14:54:54 |
| Message-ID: | 3797.1181919294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> I'd suggest allowing either full names ("swedish") or the standard
>> two-letter abbreviations ("sv"). But let's stay away from locale names.
> We can use database's encoding name (the same names used in initdb -E)
AFAICS the encoding name shouldn't be anywhere near this.
The only reason the TS stuff needs an encoding spec is to figure out how
to read an external stop word file. I think my suggestion upthread is a
lot better: have just one stop word file per language, store them all in
UTF8, and convert to database encoding when loading them. The database
encoding is implicit and doesn't need to be mentioned anywhere in the TS
configuration.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-15 15:05:06 | Re: How does the tsearch configuration get selected? |
| Previous Message | Tom Lane | 2007-06-15 14:51:34 | Re: How does the tsearch configuration get selected? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Wojciechowski | 2007-06-15 15:05:01 | Re: Change sort order on UUIDs? |
| Previous Message | Tom Lane | 2007-06-15 14:51:34 | Re: How does the tsearch configuration get selected? |