| 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 16:40:09 |
| Message-ID: | 5540.1181925609@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:
> But configuration for different languages might be differ, for example
> russian (and any cyrillic-based) configuration is differ from
> west-european configuration based on different character sets.
Sure. I'm just assuming that the set of stopwords doesn't need to vary
depending on the encoding you're using for a language --- that is, if
you're willing to convert the encoding then the same stopword list file
should serve for all encodings of a given language. Do you think this
might be wrong?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-06-15 16:49:48 | Re: How does the tsearch configuration get selected? |
| Previous Message | Teodor Sigaev | 2007-06-15 16:26:37 | Re: How does the tsearch configuration get selected? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2007-06-15 16:40:54 | Re: Rethinking user-defined-typmod before it's too late |
| Previous Message | Teodor Sigaev | 2007-06-15 16:26:37 | Re: How does the tsearch configuration get selected? |